Impact Analysis

See what breaks before you change a field.

SchemaForce maps the blast radius of any field — the rules, layouts, lookups, and automations that depend on it — and leads with a plain verdict, so you change with the full picture instead of finding out after you ship.

A small edit shouldn’t quietly break three automations. Impact analysis answers “what breaks if I change this field?” from your org’s real structure — before you touch it.

A verdict before you changeMetadata only — never your records

The blast radius of any field

Open a field and its Impact section pulls together everything that depends on it — same-object and cross-object validation rules, the page layouts that expose it, the lookups it powers, and the Flows, Apex, and workflow rules that reference it from Salesforce’s dependency graph.

Same + cross-object validation rules
Page layouts that expose the field
Lookups & master-detail it powers
Flows, Apex & workflow rules
External integrations that use it
Metadata only — names, never logic

A verdict, not just a list

Each field leads with one of three verdicts — Depends (“referenced by 4 validation rules, 3 layouts, 2 automations — review before changing”), Safe (“likely safe to retire”), or Unknown — so you get an answer first and the evidence underneath it.

On a field, on an object, or just ask

Impact shows up in three places: an Impact section on every field, an Impact tab that rolls up the blast radius for a whole object, and the assistant — ask “what breaks if I change Region__c?” in plain language.

Conservative on purpose

The “safe to retire” verdict only appears when page-layout coverage was fully captured — otherwise you see “unknown, verify before removing.” Automation links are drawn at the dependency-graph level (component names, never Flow or Apex internals) and cover custom fields. We’d rather tell you to check than call a field safe when we can’t see every layout.

Common questions

Does it tell me exactly what breaks?

It leads with a plain verdict and lists the validation rules, layouts, lookups, and automations that reference the field. Automation links are at the dependency-graph level — component names, not a parse of Flow or Apex internals — so for a high-risk change a sandbox test stays the final check.

Is it a separate plan or add-on?

No — impact analysis is part of the core dictionary, on every plan.

Do I need approval or a sales call to try it?

No. SchemaForce is self-serve — sign up, connect your org, and start. Pricing is published up front.

Do you read our data?

No. We read object and field definitions only — never the contents of your records.

See your own org in minutes.

Connect Salesforce, explore every object and field, and ask your schema anything — free to start.