The KeyRef value shown for a record doesn't follow the key order defined in the entity/projection — a child key shows before its parent key, even though the projection's key definition looks correct. Can the ordering be fixed?

All FAQ questions / Integrations and APIs

Answer

The framework's own KeyRef generation logic can't safely be changed for one entity without risking side effects elsewhere, so this isn't something to adjust globally. If the display order genuinely needs to differ for a specific logical unit, handle it as a page-level customization that reformats the KeyRef value only for display (e.g. as a derived column) — don't attempt to change the underlying stored KeyRef value itself.

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

← Browse Integrations and APIs questions