If you have edit rights on an Org Model you can fetch dependency data (specifically, where is the selected metadata used/referenced in) and visualize the dependency trees. They can be then viewed by anyone with access to the Org Model. Any PRO space with a Salesforce connection license can generate up to 50 dependency trees; for unlimited dependency analysis you need to upgrade to Enterprise license.

Article outline

  • How to generate a dependency tree?
  • How to use dependency trees?
  • On which metadata are dependency trees supported?
  • Supported dependencies 

How to generate a dependency tree?

In order to generate a dependency tree open the Org Model, select a metadata in a tree and open the IMPACT ANALYSIS / DEPENDENCY / USAGE tab in the right panel.

For custom objects and fields the dependency trees will be located closer to the bottom in the IMPACT ANALYSIS / DEPENDENCY / USAGE tab. You will have to scroll down to see them. 

Click "Run dependency analysis" (only available if you have edit rights) to start fetching the data. You will see the live status update of the operation. Once the dependency tree has been generated you will see it in the list with a time stamp when it was generated.

How to use dependency trees?

Dependency trees are opened in a new modal window. At the top you can see the data stamp of the last sync (when the org model was created/updated) and the date stamp of when the tree was generated. Ideally, these 2 dates would fall on the same day because that ensures there isn't any mismatch between the actual configuration of your Org and the analysis you are running. You can also click on "?" icon to get instructions on how to navigate around the tree. 

You can also click on "filter" and choose some metadata types to exclude from your tree (especially useful when you have e.g. too many reports!)

The dependency trees use the mixture of Salesforce dependency API and our own processing to show you the metadata that use the selected item (or more specifically, that reference the selected item). This process works recursively until all dependencies have been accounted for on each returned metadata component.   

The dependency tree is not necessarily an impact map : you will not see all metadata that are touched, updated or used by the selected metadata item. You will however see all metadata that could break / stop working if you alter or delete the selected metadata.

You can click on the name of the node in the dependency tree to inspect it. If we have it in our org model you will be able to navigate either to Salesforce setup or the reference node in the Org Model to inspect it for more details.

On which metadata are dependency trees supported?

At the moment you can generate the dependency trees on:

  • Apex classes
  • Aura component bundles
  • Flows
  • Custom objects
  • Fields 
  • Custom buttons
  • Visualforce (Apex) components
  • Visualforce (Apex) pages

Supported dependencies 

The dependency trees are not yet 100% complete. There are some metadata dependencies which are not supported by the Salesforce APIs and will require additional processing done on our side. Rest assured, we are working on supporting those missing relationships and we fully expect to enrich the trees (in terms of supported items and relationships) going forward. For the moment, here is the list of supported dependencies:

Apex classes

  • Apex classes
  • Apex triggers
  • Custom Sites 
  • Flows
  • Process Builder Workflows
  • Visualforce (Apex) pages
  • Visualforce (Apex) components
  • Web Links

Aura component bundles

  • Aura definitions

Flows

  • Actions
  • Flexi Pages
  • Lightning pages
  • Process Builder Workflows

Custom objects

  • Apex classes
  • Apex triggers
  • Flexi pages
  • Flows
  • Reports

Fields 

  • Apex triggers
  • Apex pages
  • Approval processes
  • Custom buttons
  • Email templates
  • Field sets
  • Flows
  • Formula fields
  • Global actions
  • Layouts
  • Lightning components 
  • Lookup filters
  • Process builder workflows
  • Reports (within field dependency trees we also support reports <-> dashboards dependencies)
  • Sharing Rules
  • Validation rules
  • Workflow Field Updates
  • Workflow Rules

Custom buttons

  • Validation rules

Visualforce (Apex) components

  • Visualforce (Apex) components
  • Lightning pages
  • Actions

Visualforce (Apex) pages

  • Page layouts
  • Custom objects
  • Lightning pages
  • Custom buttons

Did this answer your question?