Salesforce dependency analysis
Use sf-intelligence to trace what depends on a Salesforce field, object, Flow, Apex class, layout, permission set, integration endpoint, or package boundary before you change it.
Why Salesforce dependencies are hard to see
Salesforce dependencies live across XML metadata, Apex source, formulas, Flow definitions, Profile and Permission Set grants, page layouts, packages, and integration configuration. A single field can be referenced by automation, code, reports, validation rules, and external systems. sf-intelligence collects those signals into a local graph and reports how each dependency was found.
Dependency analysis targets
| Change target | What to inspect |
|---|---|
| Field | Formulas, Flows, validation rules, Apex references, layouts, FLS, reports |
| Object | Child relationships, automations, Apex queries, permissions, tabs, record types |
| Flow | Entry criteria, called subflows, field writes, Apex actions, scheduled paths |
| Apex class | Call graph, trigger entry points, tests, integrations, async jobs |
| Permission set | Object and field grants, app access, tab access, assigned users through live reads |
| Package | Namespaced components, local references, uninstall and upgrade blast radius |
Searches this page answers
- "Salesforce dependency analysis for custom fields"
- "Where is this Salesforce field used?"
- "What depends on this Flow?"
- "What breaks if I remove a picklist value?"
- "What Apex classes call this method?"
- "What is the impact of changing a permission set?"
Evidence-first output
The output is designed for review before a change lands. Each dependency points to a canonical component ID, the edge type, the confidence tier, and any known coverage caveat. If a metadata family was not retrieved, sf-intelligence says that the scan is partial instead of implying safety.
Related pages
For change-specific blast radius examples, read Salesforce impact analysis. For broader org inventory, read Salesforce metadata analysis. For installation in an AI client, read Claude Salesforce MCP setup.
Trace dependencies before you change metadata.
Run a read-only refresh, then ask dependency questions in plain language.