3614240 - OData is returning values not recognized on the Picklist

When OData query is performed against a field that’s associated to a picklist, values in the payload that don’t match any of the picklist’s Labels, External Codes or Option IDs. As a result:

• Some records display numeric or unexpected codes instead of the expected labels, external codes or option ids.
• Downstream processes that rely on valid picklist values fail or produce inconsistent results.

This field was previously associated with a different picklist. Although you’ve reassigned it to the new picklist, existing records still contain the old picklist values (which aren’t valid in the new picklist). OData simply reflects whatever is stored in the database, so it continues to return those legacy values.

To ensure OData only returns values recognized by the current picklist, you must update each affected record so that its stored value corresponds to a valid option in the new picklist

picklist, optionid, option id, external code, label, random, unexpected, unrecognized, odata, successfactors, picklistvaluev2, picklistoption , KBA , LOD-SF-INT-ODATA , OData API Framework , Problem