Jonathan Stegall

This issue was first mentioned in #110 as part of a WooCommerce question, which itself was at least partially fixed in #118.

We also need to put in some documentation about this. Documentation is totally not a fix for this issue, as I think it is hard to even imagine this as...

We could at least show this on the fieldmap add screen as help text, close to the WordPress field picker.

We have a branch for this issue now. https://github.com/MinnPost/object-sync-for-salesforce/tree/119-new-meta-fields

The reason I mentioned this is that this issue is deeper still, in which meta fields don't get added when an object is created, but after as a subsequent update.

Salesforce documents this error at [https://help.salesforce.com/articleView?id=000250168&language=en_US&type=1](https://help.salesforce.com/articleView?id=000250168&language=en_US&type=1). It is not particularly helpful though.

This is an interesting post as well: https://salesforce.stackexchange.com/questions/9322/what-does-a-restricted-picklist-mean > In addition to @LaceySnr 's thorough documentation, this bad value for restricted picklist field: error will occur if you are setting...

And just for kicks, I posted a question about this to StackExchange. https://salesforce.stackexchange.com/questions/202368/api-error-bad-value-for-restricted-picklist-field

This is a Salesforce configuration error. Here's what I had to do (in Salesforce): 1. Go to Setup 2. Customize -> Opportunities (I am testing with an opportunity picklist at...

The API does not seem to change the data it sends when values are moved from Available Values to Selected Values. I think there's nothing we can do about this,...