DEPENDENCY MAP

SALESFORCE FIELD DEPENDENCY WORKBOOK.

Before you change, retire, or clean up a custom field, see what references it. Dependency Map evaluates the custom fields on one selected object and maps detected references across Apex, Flows, Workflow Rules, Validation Rules, formula fields, Reports, and Page Layouts into a review-ready workbook.

Read-only · No package install · No Connected App · Paid XLSX workbook

Opens dependencymap.keelcadence.com. Best run from desktop, since the diagnostic uses your active Salesforce browser session.

Cleanup Review

Cleanup Review — 15% off Field & Object Audit and Dependency Map.

Use them together when your cleanup review calls for both. Each diagnostic runs independently and produces its own XLSX workbook. Run Field & Object Audit to surface cleanup review candidates, then use Dependency Map to review detected references within evaluated coverage before you make a change.

Enter code CLEANUP15 at checkout on either or both tools. Each purchase is billed and delivered separately.

Overview

WHAT THIS REPORT IS FOR.

Deleting or repurposing a Salesforce field that is quietly referenced elsewhere can break Flows, automations, formulas, and reports without warning.

Dependency Map gives admins and consultants a selected-object workbook for reviewing what references a field before they change, repurpose, or retire it.

What references this field, and is it safe to review changing it?

What Gets Evaluated

Apex Classes & Triggers
Flows
Workflow Rules
Validation Rules
Formula Fields
Reports
Page Layouts & Field Sets
Lookup Filters

Evaluates the custom fields on one selected object per run. Findings are labeled Direct or Heuristic, and the Coverage & Collection record shows exactly what was evaluated, scope-capped, permission-limited, or intentionally not evaluated in V1 — so an empty category reads as not evaluated, not confirmed clean.

WHEN TO RUN THIS DIAGNOSTIC.

  • Before you change, repurpose, or retire a custom field.
  • Before deleting a field you suspect is unused.
  • When you need evidence before a cleanup or deprecation decision.
  • Right after inheriting an org with unclear field history.
  • When a stakeholder asks what depends on a specific field.

THIS WORKBOOK IS USEFUL WHEN.

  • You are about to delete, repurpose, or retire a custom field.
  • You need evidence before a cleanup or deprecation decision.
  • You are documenting field dependencies for a handoff.
  • You want a workbook before discussing a field change with a client or stakeholder.

DIRECT VS. HEURISTIC, NEVER BLENDED.

Every reference Dependency Map finds is labeled Direct or Heuristic. Direct references are explicit, structural matches — a Flow element, a formula, or a Validation Rule that names the field. Heuristic references are source-text matches that require manual verification, and they are never counted toward Review Priority.

The Coverage & Collection record on every results page shows exactly which categories were evaluated, scope-capped, permission-limited, or not evaluated in V1 for that run, so a category with no findings reads as not evaluated, not confirmed clean.

What You Get

WHAT THE WORKBOOK INCLUDES.

The paid workbook is designed to be a field-change review artifact, not a raw metadata export.

Cover summary with run scope and object details

Deduplicated Dependency Findings, with evidence detail per reference

Field Review — one row per field, prioritized for review

Flow element-level evidence

Direct vs. Heuristic labels throughout

Coverage & Collection record

Review Tracker with built-in dropdowns, for handoff and documentation

Methodology & Legend

Free Summary

WHAT THE FREE SUMMARY SHOWS.

Free · On-Screen

The free on-screen summary gives a selected-object view of dependency findings before purchase. It includes counts for custom fields evaluated, direct references found, heuristic references, fields with no direct references detected, and High Review Priority fields.

The full XLSX workbook includes the detailed findings, evidence, Field Review prioritization, and Review Tracker.

WHAT THE REPORT HELPS YOU DECIDE.

  • Which fields carry the most detected references and deserve review first
  • Which fields show no direct references within evaluated coverage
  • Which Flow elements, formulas, or Validation Rules touch a given field
  • Which findings require manual verification before you rely on them
  • Which fields are safe to move into a cleanup or retirement plan, once findings are validated
Access & Limits

WHAT THIS REPORT DOES NOT CLAIM.

  • It does not claim to find every dependency, and it does not produce a complete dependency graph.
  • It does not tell you a field is safe to delete.
  • Some categories are intentionally not evaluated in V1 — see the results page's Coverage & Collection detail.
  • Report coverage is always limited to what the connecting user can see in Salesforce.
  • It does not modify Salesforce configuration or records.
  • It does not read customer record values, files, attachments, or report result rows.
  • Heuristic references require manual verification and are never counted toward Review Priority.

Dependency findings require validation. Use the workbook to identify review candidates, then confirm each finding against the evidence detail before changing Salesforce configuration.

TRUST MODEL.

  • No package install
  • No Connected App setup
  • Read-only diagnostics
  • No Salesforce writes
  • No permission changes
  • No customer record values, files, or report result rows retrieved
  • Free on-screen summary before purchase
  • Paid downloadable XLSX workbook
  • 90-day report retention
  • Email-first product support

Why a bookmarklet instead of OAuth?

KeelCadence uses a browser-session-based connection so admins can run a diagnostic without installing a package, creating a Connected App, granting a long-lived OAuth refresh token, or giving KeelCadence persistent Salesforce access. The session is used only to read the metadata and aggregate signals needed for the diagnostic workbook. It does not create, update, or delete Salesforce records.

Common Questions

Common questions.

IS THIS A COMPLETE DEPENDENCY GRAPH?+

No. Dependency Map maps detected references within evaluated coverage for the custom fields on one selected object. It does not claim to find every dependency and does not tell you a field is safe to delete.

DOES IT CHANGE SALESFORCE?+

No. The diagnostic is read-only. It does not create, update, delete, or modify Salesforce configuration or records.

WHAT'S THE DIFFERENCE BETWEEN DIRECT AND HEURISTIC REFERENCES?+

Direct references are explicit, structural matches — a Flow element, formula, or Validation Rule that names the field. Heuristic references are source-text matches that require manual verification, and are never counted toward Review Priority.

HOW IS THIS DIFFERENT FROM IMPACT AWARENESS?+

Impact Awareness reviews selected-object readiness factors — required fields, record types, validation rules — before imports and bulk changes. Dependency Map answers a narrower question: what references this specific field, before you change, repurpose, or retire it?

CAN I SEE A SAMPLE BEFORE I RUN IT?+

Yes. A sample on-screen summary with fictitious data is shown on the Dependency Map landing page before you connect an org or purchase.

Get Started

SEE WHAT REFERENCES THE FIELD.

Run a read-only Dependency Map review to see detected references across Apex, Flows, Workflow Rules, Validation Rules, and more before you change, repurpose, or retire a field.

KeelCadence uses session cookies and Google Analytics 4 for site usage insights. GA4 does not receive Salesforce credentials, Org IDs, Report IDs, or payment data. You can opt out for this browser.