Attempts to validate or deploy a change set may result in the following error message:
In the field: searchResultsFields - no CustomField named Custom_Object__c.Custom_Field__c found
Note: In this example, 'Custom_Object__c.Custom_Field__c' in the error above refers to the problematic object and field API names. These may be different depending on your custom object and field names.
See Select Components for an Outbound Change Set for details on accessing the affected outbound change set.
1. Click the 'Add' button under the 'Change Set Components' heading.
2. Select 'Custom Field' in the 'Component Type' pick list.
3. Choose the problematic field from the list.
In our example error above, the affected field's API name is 'Custom_Field__c'. For more details on identifying the corresponding label based on the field's API name, refer to Find the API name of a field.
4. Click 'Add To Change Set'.
5. Re-upload the outbound change set. See Upload an Outbound Change Set for more details.
000384462

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.