Custom fields could previously be added to LU ShopOrd, but the client now shows 'This logical unit cannot have custom fields,' even though ShopOrd doesn't appear in the Excluded Logical Units window — what changed, and how do you fix it?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Refresh the Dictionary Cache — this specific 'cannot have custom fields' message can appear when the client is reading a stale cached view of which logical units are excluded, out of sync with what the Excluded Logical Units configuration actually currently shows. Refreshing the Dictionary Cache resolved this for a confirmed case without needing any change to the Excluded Logical Units setup itself.

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