Find Where a Field Is Used
Find out where a custom field is referenced, such as in a formula or Apex class, with a click of the Where is this used? button. You can see where a field is used and where changes to the field appear before you edit it.
Required Editions
| Available in: Salesforce Classic and Lightning Experience |
| Available in: Professional, Enterprise, Performance, and Unlimited Editions |
| User Permissions Needed | |
|---|---|
| To view references: | View Setup |
On a custom field’s detail page, click Where is this used? to see the field reference details. To view the settings for the layout, formula, or other reference, click a reference label.
The list can include these references.
- Active validation rule
- Layout
- Formula field
- Visualforce page
- Apex class
- Apex trigger
- Email template (Salesforce Classic, text based)
- Field set
- Flow (query)
- Lightning component markup (attr)
- Process Builder (criteria)
- URL button (formula)
- Lightning page (Related List–Single and Dynamic Related List–Single components)
- Lookup filter (lookup and master detail)
- Report (column, filter)
Considerations for Finding Fields
- References to reports on objects where there’s a foreign key relationship don’t appear. For example, if a custom object has a lookup relationship to Account or any standard object, and the custom fields of Account are added to a report of type CustomObject with Account, then the report isn’t listed for the custom fields on Account.
- Reference labels link to more information only if there‘s a known settings page for the reference. For example, a report name links to the report settings. But a criteria formula created within a flow doesn’t link to the flow settings.
- Within a subscriber org, references in a managed package aren’t included in the list of results. For example, a number field is referenced in a formula. If you add the field to a package and then install the package in a subscriber org, the subscriber org’s field reference detail page doesn’t show that this number field is referenced in a formula field. But new references that are created after installing the managed package in the subscriber org do appear. For example, after you install the managed package and you add the number field to another formula in the subscriber org, the new reference appears.
- Only the IDs of reports that are accessible to the user initiating the query are returned. For example, if an admin creates a report and saves the report in a private folder, then the report isn’t listed in the reference detail page for a standard user.
- Joined reports aren’t supported and aren’t displayed in the reference detail page.
- The list of field references is limited to the first 2,000 entries and sorted alphabetically by reference type.
Did this article solve your issue?
Let us know so we can improve!

