A custom tab built with a master-detail association (a custom entity linked to a standard projection like CompanySiteHandling via a shared key) doesn't automatically populate the parent's key value on new child records, and removing the binding shows records from every site instead of just the parent's.

All FAQ questions / Platform, Aurena, and customization

Answer

This is achievable, but a specific detail commonly trips it up: don't add a lookup/LOV to the bound key field (like the site/contract key) in the list's field definition — since it's a bound key tied to the association, it should be left to simply inherit the parent record's value automatically rather than being presented as something the user selects, and adding a lookup to it is what breaks the automatic population and site-scoping behavior.

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