A field is genuinely editable on a screen's single-record detail/form view, and a custom field pulling that same value can be added as a column on the overview/list screen — but that new overview column stays read-only rather than becoming editable the way the original field is on the detail form.

All FAQ questions / Platform, Aurena, and customization

Answer

This is very commonly a deliberate design limitation rather than something specific to the custom-field mechanism. Many fields shown together on one tab of a detail form actually live in different underlying tables, with parent-child or referential-integrity relationships that an overview grid can't safely represent or enforce for direct inline editing. If a field isn't editable from the overview, there's usually a structural reason IFS designed it that way; whether a specific field can genuinely be made editable from the overview depends heavily on the exact field, form, and table structure involved, rather than there being one general technique that always makes an overview column editable.

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