It appears that until this morning, the API was able to handle Dropdown custom fields on contacts set to values that were not in the dropdown list, but it now rejects them. This appears to have changed around 9am Pacific time today, which is causing significant problems for us. I would just change the fields to text fields because I don’t really need the values enforced on these fields, but that doesn’t appear to be possible.
Help?
Hi @Jim_Winstead, we are looking into this and it will be fixed shortly.
Looks like the actual problem is that we had a Dropdown custom field where it hit the limit of variations. So the dropdown had like 10 variations configured, but we have gone over 499 variations that had been submitted. We’ve been able to work around it in the short term and will probably just migrate these to Text custom fields in the long term (but will have to do a dance around the 150 custom field limit to get there).