Know what breaks before you change a field, flow or Apex class.
Pick a field, object or Apex class and a change type. aprity returns everything downstream that depends on it — formulas, validation rules, flows, Apex, reports, layouts — computed deterministically from your metadata. The same question always returns the same answer, so it is safe to act on, not a best guess.
What is Salesforce impact analysis?
Salesforce impact analysis answers one question before a change ships: if I delete, modify or rename this field, object or Apex class, what else breaks? aprity builds a dependency graph across code, automation and configuration, then computes the downstream set for the component you pick — deterministically, so the blast radius is the same every time and verifiable against the metadata it came from.
The dependencies you can't see are the ones that break.
Dependencies are hidden
A field feeds a formula, that formula gates a validation rule, that rule is referenced by a flow. By hand, the chain is easy to miss.
Native tooling is partial
Where-is-this-used coverage varies by component type and rarely spans code, automation and configuration in one consistent view.
A miss ships a regression
Delete or rename the wrong field and something breaks in production — found by users, not by the change review.
Computed from metadata. Not inferred by an LLM.
The dependency graph is built locally and reproducibly. The AI only narrates the result — it is never in the path that produces the answer.
Read-only extraction
A read-only connector reads metadata only — never your records. Nothing is written back; raw metadata is purged after each scan.
Build the dependency graph
aprity computes a graph across fields, formulas, validation rules, flows, Apex, reports and layouts — locally and reproducibly.
Compute the blast radius
Pick a component and a change type — delete, modify, rename — and get the full downstream set, each link explained with a citation.
Reproducible, complete, and explainable.
Computed, not guessed
Built from metadata, not inferred by an LLM — the answer is verifiable against the source.
Reproducible
The same component and change type always return the same downstream set.
Node-level detail
Walk the graph and see what each node reads, writes and calls next.
Safe to act on
Deterministic results a change reviewer can rely on before approving the work.
Every change review, cleanup and refactor.
Change reviews
Attach the downstream impact to a change request so reviewers approve with the full picture, not a hunch.
Cleanup & deprecation
Before deleting an unused field or class, confirm nothing still depends on it — and find what does.
Refactors & release planning
Scope a refactor by its real blast radius, and sequence releases around what actually couples to what.
More detail on the security and trust page.
Salesforce impact analysis — FAQ
What is Salesforce impact analysis?
Salesforce impact analysis answers a single question before you make a change: if I delete, modify or rename this field, object or Apex class, what else breaks? aprity computes the downstream dependencies deterministically from your metadata — formulas, validation rules, flows, Apex, reports and layouts — so you see the full blast radius before you touch anything.
How is this different from Salesforce's where-is-this-used or the Dependency API?
Native where-used coverage is partial and varies by component type. aprity builds a complete dependency graph across code, automation and configuration, computes it the same way every time, and explains each link in business language with a citation back to the metadata — so the answer is both broader and reproducible.
Is the result deterministic and safe to act on?
Yes. The graph is computed locally, not inferred by an LLM, so the same component and change type always return the same downstream set. The AI only narrates the result; it is never in the path that produces the dependency answer.
Which change types does it cover?
Deletion, modification and renaming of a field, object or Apex class. aprity returns what depends on the component so a change reviewer can judge the risk and plan the work.
Does running impact analysis touch my org?
No. aprity reads metadata read-only — never your records — and cannot modify schema, data or configuration. Raw metadata is purged after every scan; only the derived documentation and graph remain, encrypted in Azure.