Salesforce Impact Analysis Tool
Analyze Salesforce metadata dependencies to evaluate risk and prevent regression bugs.
Definition
Salesforce Impact Analysis is the practice of evaluating metadata dependencies to predict the side effects of changing, refactoring, or deleting a component (e.g., custom field, class, or flow) within an org.
Overview & Context
Deleting a custom field or refactoring an Apex utility in Salesforce often causes silent regressions across Validation Rules, Flows, or other code files. SF Analyzer maps these links using the Tooling API's MetadataComponentDependency relation, letting you inspect the dependency chain locally.
Important Architecture Notice
SF Analyzer strictly enforces the local data boundary. Your Salesforce metadata, credentials, and source files never leave your system.
TL;DR (Too Long; Didn't Read)
Trace metadata relationships in your Salesforce org to identify which components depend on a custom field or class before you modify it.
Key Advantages
- Bidirectional TracingShows both what a component calls (Depends On) and what calls it (Used By).
- Data Model ERDVisualizes object relationships, lookups, and master-detail paths in ReactFlow.
- Coverage GuardWarns if your generated technical documents omit critical dependent components.
Typical Use Case
Used by release managers, testers, and Salesforce developers during sprint planning, refactoring tasks, or technical debt removal campaigns.
Analysis Workflow
Execute dependency queries against the Tooling API during the local snapshot assembly.
Isolate relationships between custom components and map caller/callee directions.
Review dependencies dynamically in the ERD data model or individual wiki pages.
Check coverage gaps in custom documents using the built-in dependency neighbor analysis.
How It Compares
Compare the secure local-first workflow against traditional cloud-based SaaS vendors.
| Dependency Insight | Salesforce 'Where is this used?' | SF Analyzer Impact Analysis |
|---|---|---|
| Apex Class References | Supported only for fields, not for class-to-class | Extracts bidirectional links for all code components |
| Flow Dependencies | Partially shown in builder; hard to export | Full list of fields, objects, and subflows referenced |
| Visual Mapping | Not available in Salesforce Setup | Interactive ERD with search, filters, and neighborhood focus |
| Local Inspection | Requires logging into Salesforce UI | Offline search and navigation in Markdown wiki files |
Frequently Asked Questions
Find answers to technical and operational questions about Salesforce Impact Analysis Tool.
Q:Can I see impact analysis for Managed Packages?
Yes. If custom Apex classes or Flows reference components inside a managed package, those dependencies are tracked, allowing you to see the impact of package upgrades on your custom code.
Q:How does the Neighborhood focus work in the ERD?
The ERD panel lets you search for any object and focus solely on its immediate connections (1-degree neighbors), hiding standard clutter to keep the schema readable.
Ready to assess your Salesforce Org?
Download the SF Analyzer desktop application. Connect your sandbox or production org via the CLI, and run the assessment 100% locally.