A well-designed configurator is often factored into many different entities (like configurators, tables, functions, workflows, and the like). When administering your environment, you don't want to mistakenly delete an entity that is still in use. Such a deletion would break any other entity relying on it. For example, if you delete a table used by a configurator, then the configurator would no longer function.
Dependency tracking helps you manage these relationships.
Dependency Tracking requires updating your entities.
This feature is available only on entities that have been modified after May 1, 2026. Any entities with modification dates before May 1 will have missing dependency information, and the tables shown in the screenshots below will be blank or incomplete.
We encourage you to open and save all the entities you wish to track. For example, if a table is used by an active configurator, open and save both the configurator and the table. If a configurator is not actively used, and is only kept in your DEV org for historical purposes, then it does not need to be opened and saved.
Dependency Information Available
When an administrator is editing most entities, a new "Dependencies" tab is visible. This tab lists many of the related items the entity depends on or is required by. Click the name of the entity to view it in a new window.
This same dependencies list appears for scenes in the new "refs" tab visible in the left toolbar.
Breaking Dependencies Discouraged
Furthermore, when actually deleting most entities, if the deletion breaks a dependency you are now warned and must confirm the deletion.
