What about Parametrized- Dynamic Query lookups in v13 (13.0.1)?
I have an attribute- lookup string in Project object
in "Project Edit" view, it works fine.
in "Project List" view. The cell for this field is showed void
Editing this cell It opens the correct lookup (and the displayed values are right; related to the parametrized field (pruid))
After chose a value, the value is displayed in the cell
After click "Save" button, the cell is showed void, but from "Edit" view I can see the value selected previously.
and after some tests, I began receiving error "HTTP 500 Internal server error" when edit cell.
is there any new for ver. 13?
I couldn't find references to this limitation in official documentation...
Dave wrote:
Parameterized lookups only work on the object CREATE / EDIT views, not the LIST view. :sad
--
Is it possible to re-design your "problem" such that it only needs a single NON-PARAMETERIZED lookup?
You can build filters (drop-downs) WITHIN lookups - so what I am suggesting here is that you are moving the "first (static) lookup" onto the filter section of the "second lookup" rather than having 2 separate attributes on your custom object itself.
You can control the "display value" of the non-parametrised lookup so it says "Pune / Dapori" even though the underlying data has just persisted the value associated with "Dapori"