A custom field added to a query-based logical unit (one with no real base table behind it) shows correctly as read-only but can't be entered/saved from the client.

All FAQ questions / Platform, Aurena, and customization

Answer

This is expected for a query-based LU, not a bug — because it has no base table of its own (it assembles data from elsewhere), there's nowhere for an entered value to actually be persisted against that LU, so a persistent custom field added to it will display but can't accept input.

Related procedures and examples

• Confirm a writable entity before creating a field

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