A persistent custom field configured with a List of Values (LOV) that references a Custom Logical Unit (which has four fields) only shows one of those four fields in the LOV search popup, instead of all four — how do you get the other fields to show up as selectable/visible columns in that LOV?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Check the individual field-level LOV checkbox on the Custom Logical Unit's own fields, not just the persistent custom field that references it — each field on the CLU that you want visible in the LOV popup needs its own LOV checkbox enabled. Once that's set on the relevant fields, you can then configure how those fields appear (order, visibility) directly within the custom field's own LOV configuration settings, and all four fields become available in the search popup rather than just the one that was previously flagged.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions