Trying to connect a custom reference-type field as the parent key when building a custom tab throws 'The connected key CF$_X is a custom reference and cannot be used in a parent key connection' — how should a key field like this be built instead?

All FAQ questions / Platform, Aurena, and customization

Answer

A custom field being used as a parent key connection for a custom tab needs to be a plain persistent field (e.g. Text type) rather than a Reference-type field — a Reference-type custom field can't serve as a parent key connection, likely because it would create a circular resolution between the reference's own lookup and the tab's key linkage. Recreate the field as a persistent, non-reference field holding the same value, and use that for the parent key connection instead.

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