Training Check Component References

Training: Check Component References

What you'll learn: how to see which application components depend on which — impact analysis before you change or delete anything. You need: Administrator or Developer access type in an application (UI label "Tenant"). Time: 5 minutes.

Before you start

Every screen, flow, document, and route that uses a data model (or another component) is recorded as a component reference. Before changing a model or removing a screen, check here to see what would be affected.

Steps

1. Go to Left menu → Components → Component References. (Fallback: header Search → "Component References".)
2. Use the filters — Source Application Component Type and Target Application Component Type — to narrow the question. For example: Source Screen, Target Data Model answers "which screens read which models?"
3. Click the search button. Each row links a Source Component to the Target Component it depends on — for example, screen Training Parts → data model TrainingPart.

Check your work

A screen generated from a data model shows a row per dependency (the screen's table element and its target model). Component names link to the component's detail page.

Try it yourself

Filter with Target = a data model you plan to change and review every source that touches it. Also see Components → Component Changes for the audit trail of recent edits, and Components → Modules for how components group into modules.

Related training

Training: Generate a Screen from a Data Model · Training: Create a Data Model