A standard field exists on an entity but can't be exposed directly on a specific overview screen through configuration — is a custom field the only way?

All FAQ questions / Platform, Aurena, and customization

Answer

Confirm this limitation for your specific release before committing to a workaround — exposing a standard field that isn't natively available on a given overview screen has, in at least one confirmed case, required creating a read-only custom field that surfaces the same underlying value, rather than there being a direct "add standard field" option for every field on every screen.

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

← Browse Platform, Aurena, and customization questions