Salesforce Metadata Dependency Analysis

Understand where Salesforce metadata is used before you change it.

Org360 turns cached Salesforce dependency context into a practical impact view so admins can understand where metadata is used before they deactivate, rename, or replace it.

Start your 14-day free trialBook a demo

Where used

Known incoming references

What it uses

Known outgoing dependencies

Grounded context

Findings, changes, and score history

Visible limits

No false completeness claims

Move from raw metadata to actionable context.

Org360 keeps the evidence, health impact, and next action together so Salesforce teams can investigate without reconstructing context by hand.

Answer where-used questions

Start from a field or metadata component and review the known components that reference it or that it depends on.

Inspect a dependency graph

Use a focused graph and compact tables instead of reading a long conversational answer or searching metadata manually.

Add health and change context

Investigate dependencies alongside open findings, recent changes, score history, and the latest cached metadata snapshot.

Work cache-first

Normal investigation uses the metadata already collected for the active org and does not expose Salesforce OAuth credentials to the browser.

How it works

A read-only workflow turns Salesforce setup signals into a persistent, reviewable history.

  1. STEP 1

    Select a component

    Start from a field, Flow, rule, or another cached metadata component.

  2. STEP 2

    Load known edges

    Read incoming and outgoing relationships from the tenant-scoped dependency graph.

  3. STEP 3

    Add current context

    Bring in related findings, recent changes, and health history.

  4. STEP 4

    Review impact

    Use the graph and evidence to plan the next safe investigation step.

Inside Org360

See the known impact before making a change.

Impact Analysis centers the selected component and separates incoming references from the metadata it uses.

Dependency coverage varies by metadata type and by what Salesforce exposes. Org360 shows the available graph and does not claim that an empty result proves a component is safe to remove.

Discount GuardrailType: Validation RuleSignal: References field
Opportunity RenewalType: FlowSignal: Reads field
Revenue OperationsType: Permission SetSignal: Grants field access

Explore the connected Org360 workflow

Org health, change memory, and investigation are designed to work together rather than as isolated reports.

Metadata change trackingReview what changed before a dependency or finding appeared.Connected App monitoringDetect access-policy changes that can expand external access to the org.

14-day Pro trial

Bring continuous context to your Salesforce org health.

Connect your Salesforce org and use every Org360 Pro feature for 14 days. No credit card required.

Start your 14-day free trial
Salesforce Metadata Dependency Analysis | Org360