All docs pages (49)
How do I find where a field is used in Salesforce?
In Setup, open the custom field and click Where is this used? SFDC Police lists its references and marks which automations read or write it.
Updated 2026-11-09
For a custom field, open the field in Setup and click Where is this used?. Salesforce lists the layouts, formulas, Apex, flows, reports and other places that reference the field, up to 2,000 entries. SFDC Police reads Salesforce's dependency data (the MetadataComponentDependency object) from a field label on a record page, and for flows, triggers and Apex classes it opens the source to show whether each one reads or writes the field. Neither list sees every use, so treat an empty result as "nothing recorded", not as "safe to delete".
In Salesforce Setup
- From the object management settings for the field's object, go to Fields (Manage Fields for a Specific Object).
- Click the field label.
- Click Where is this used?. To open the settings of a layout, formula or other reference, click its label.
You need the View Setup permission. The list can include active validation rules, layouts, formula fields, Visualforce pages, Apex classes and triggers, field sets, flows, lookup filters, Lightning pages and reports (columns and filters) (Find Where a Field Is Used).
The same article lists what the button does not show:
- Reports that reach the field through a lookup from another object (for example, an Account custom field in a report on a custom object with Account).
- In a subscriber org, references inside an installed managed package. References you create after installing it do appear.
- Reports you can't access, such as a report another user saved in a private folder.
- Joined reports.
- Anything past the first 2,000 references.
The article describes the button on a custom field's detail page only.
With SFDC Police
From a record page:
- Open a record of the object in Lightning Experience.
- Hover the field's label. The SFDC Police tooltip appears. Click the label to pin it open.
- Click Automations.
For a custom field, the tooltip shows Where this field is used: how many automations write it, read it or are unclear, and how many other uses there are. The list is grouped into Automation & code, Apex tests and Layouts, reports & other, and names link to the item in Salesforce where a link is available. To tell reads from writes, SFDC Police opens the source of up to 60 flows, triggers and Apex classes per lookup. Anything it did not open, or could not read (for example managed code), is marked References, and the tooltip says so.
To explore further, open Metadata > Where Used in the extension (also under All tools in the floating panel). Search part of the field's API name without __c, pick the result, and you see Used by (what references it) and Uses (what it references). Click any item to explore it in turn. This view does not mark reads and writes.
What SFDC Police can't see:
- Salesforce documents MetadataComponentDependency as a Beta feature. Through the Tooling API it returns no more than 2,000 records per query and does not include reports (MetadataComponentDependency). For reports, use Setup's Where is this used?.
- For a standard field, the tooltip does not use this data. It uses a Process Graph scan of the object's automations instead, and offers to run one if none exists. Where Used search finds custom fields, Apex classes and triggers only.
- If Salesforce returns its 2,000-reference maximum, the tooltip says there may be more.
For the "is it still used?" question across a whole object, open Metadata > Unused Metadata, choose Custom Fields, pick the object and click Find unused. It lists the object's custom fields outside any managed package namespace that have no recorded references, with their last-modified date and an Export CSV button. It compares against at most 2,000 custom field references for the whole org; when that cap is hit, the page says to treat the results as partial. The page calls these candidates to review, not fields that are safe to delete.
Before you delete a field
- Check both lists: SFDC Police for automations and read/write, Setup's Where is this used? for reports. Ask report owners about private-folder and joined reports, which Setup's list leaves out.
- Ask the owners of integrations, data loads and managed packages that use the field.
- Salesforce won't let you delete a custom field that is referenced elsewhere, for example by a field update or Apex. Deleting needs the Customize Application and View All Data permissions (Delete a Custom Field).
- Deleting a field deletes its field history data. You can restore the field and its data for 15 days, or until your org permanently deletes it, whichever comes first (same source).
- A restored field keeps a
_delsuffix on its developer name, and a restored formula field stays disabled until you edit and save it. A deleted field counts against your custom field limits until it is hard deleted (Manage Deleted Custom Fields).