Apex Code Development You need to sign in to do that
Don't have an account?
Bad value for restricted picklist field, eben though the picklist has the value
Hello,
I have a custom field on the Account object (no record types) which uses a global picklist. We have built a REST web service and are passing a value for this picklist. Even though we are passing the same value in the web service, we are facing the issue "INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST, Primary Marketplace: bad value for restricted picklist field: Myntra: [Primary_Marketplace__c]"
Screen shot of the global picklist:-
And the Primary Market place custom field's screen shot which uses this global picklist
Any inputs as to what might be wrong here??
Regards,
Gautam.
I have a custom field on the Account object (no record types) which uses a global picklist. We have built a REST web service and are passing a value for this picklist. Even though we are passing the same value in the web service, we are facing the issue "INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST, Primary Marketplace: bad value for restricted picklist field: Myntra: [Primary_Marketplace__c]"
Screen shot of the global picklist:-
And the Primary Market place custom field's screen shot which uses this global picklist
Any inputs as to what might be wrong here??
Regards,
Gautam.
I got the issue. Apologies, was a mistake from my end. The contact object also had a field whose API name was the same, hence the confusion. The custom field in the Contact Object did not have the required values in the gobal picklist.
All Answers
Could you please double check the value you are getting in debug log?
Some thing wrong with the value only either wrong or incorrect.. You can remove the restricted clause and try to create record, then check the picklist value.
I did check the value but was of no help as the value in the logs was exactly the same as in the picklist field.
Also, I don't think we can remove the restricted clause from the setup. Is there a way to do it??
I got the issue. Apologies, was a mistake from my end. The contact object also had a field whose API name was the same, hence the confusion. The custom field in the Contact Object did not have the required values in the gobal picklist.