You have created a formula for a formula field, workflow rule, process, validation rule, etc. and it's working for all values except for one.
The ISPICKVAL() function in Salesforce formula fields, workflow rules, validation rules, and Process Builder evaluates whether a picklist field contains a specific value. ISPICKVAL() uses the API Name of the picklist value — not the label displayed to users. If a picklist value was renamed after the formula was written, the API Name may no longer match the visible label, causing the function to return unexpected results for that value.
For example, if you have a custom 'Fruit' picklist with values including 'Apple', 'Banana', 'Cherry', and 'Durian', and your ISPICKVAL formula stops returning the correct result for 'Cherry', the issue may be that 'Cherry' was renamed and its API Name still reflects the original value.
Example:
You have a custom "Fruit" picklist field with the following values: "Apple," "Banana," "Cherry," "Durian," ...
You have created a formula field that will return A, B, C and D respectively if the corresponding picklist value is selected. Apple, Banana, Durian and everything else is working except for "Cherry."
Navigate to the picklist field used in the formula and look for the picklist value that was not working. Check if the "API Name" listed for the picklist value is exactly the same as the one shown in the "Values" column. If not, use the API Name instead for the ISPICKVAL() function in the formula. It should work afterwards.
The ISPICKVAL() function uses the API Names of the values and not the actual values itself. Usually these values are the same but if the picklist value had been renamed, the API Names are not changed unless manually modified to match the new picklist value name.
For example, if the API Name for the renamed value is still 'Cheery' (original value before rename), update your formula from ISPICKVAL(Fruit__c, 'Cherry') to ISPICKVAL(Fruit__c, 'Cheery') to match the API Name.
000380973

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.