Adding a custom field to a specific Aurena page works fine on most pages, but on one particular page, backed in IEE by one specific Logical Unit, Page Designer won't let a new custom attribute be added to that page's Content at all. Is there a general limitation on which pages/lists support custom attributes?

All FAQ questions / Platform, Aurena, and customization

Answer

A page's apparent LU in IEE isn't necessarily the actual Logical Unit backing its Aurena projection's underlying view — trace the specific view a given Aurena page/list actually reads from via the Debug Console to find its real backing LU, which can sometimes differ from what IEE shows, and can even change from one Update level to the next. Separately, note that a Logical Unit without its own base table, a view-only/joined LU rather than one backed by a real physical table, generally only supports ReadOnly custom fields rather than full read/write ones — if the page's real backing LU turns out to be this kind of table-less LU, that's an inherent limitation of extending it, rather than a bug or missing permission.

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