An attribute connected to a Custom Logical Unit was added to a List of Values, but the search window still shows that field as empty, even though a similar existing attribute on the same custom view works fine in the search window — refreshing/reloading the configuration doesn't help.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Restart the user's client session entirely, rather than relying on an 'Update' or 'Reload Configuration' action — some metadata changes, like adding an attribute to a List of Values connected to a Custom Logical Unit, only take effect after a full session restart; refreshing or reloading configuration in place doesn't propagate this specific kind of change. Logging out and back in (or fully restarting the client) is what actually makes the new attribute populate correctly in the search window.

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