By default, Salesforce indexes only a limited set of fields per object for Salesforce Global Search. The indexed fields for each object are defined in Salesforce documentation and may not include all field types by default. Fields such as picklists, lookup fields, formula fields, and currency fields are typically not indexed for search.
If users need to search records by a field that is not indexed by default, administrators can use a workaround: create a custom text field (which is always indexed for Global Search on custom objects) and automatically populate it with the desired value using a Salesforce Flow.
For the default list of searchable fields by object, see:
Before implementing this solution, evaluate whether the workaround is appropriate for your org's scale and requirements.
Note: Populating a large number of records (several thousands) with identical field values in a custom text field may not be a scalable solution. This can result in search crowding or truncation, where Salesforce returns too many results matching the same value. Review the Help Users Find Missing Records documentation (in Additional Resources) for implications.
Also consider whether search filters could provide an alternative approach to help users narrow results without requiring additional indexed fields. See the Configure Salesforce Search documentation in Additional Resources.
Create a custom text field on the object whose records you want to make more searchable. Since this field is used only for search indexing purposes, do not add it to page layouts.
Refer to the Create a Custom Field article in Additional Resources for step-by-step instructions.
Create a Salesforce Flow to automatically populate the custom text field with the value you want to make searchable whenever a record is created or updated.
Use the following Flow configuration:
Add an Update Records element to the Flow with the following settings:
$Record > choose the source field you want to make searchableSave and Activate the Flow.
The Flow will automatically populate the custom text field for new records going forward, but existing records must be updated manually. See the Mass Update Records in Salesforce and How to Retroactively Trigger a Workflow on Existing Records articles in Additional Resources for instructions.
If users are still unable to locate records after completing these steps, see Unable to Find Records in Global Search in Additional Resources for additional troubleshooting.
Searchable Fields by Object in Salesforce Classic
Search Manager (Lightning Experience)
Help Users Find Missing Records (Search Crowding)
Mass Update Records in Salesforce
How to Retroactively Trigger a Workflow on Existing Records
Limitations of List View Search
Cannot See All Contacts Associated to an Account When Searching for Account Name
000382100

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.