On a push, this usually happens when there’s a Salesforce API error. If you have logging enabled on the plugin, you should see error logs. If not, please enable the logs and see what error messages there are.
Thread Starter
enils7
(@enils7)
I turned on logging of errors (and just learned where logs go in WP – thank you!).
I got this error-
URL: https://na73.salesforce.com/services/data/v42.0/sobjects/Contact/Email/erika%2Enilson%40gmail%2Ecom
Message: Json Deserialization failed on token ‘null’ and has left off in the middle of parsing a row. Will go to end of row to begin parsing the next row
Code: 400
~~~~~
I looked this up in SF support and someone mentioned it was likely a data issue and not a match issue. This makes sense since the new user I created had a unique email address to both WP and SF, so there is no matching that is occurring, it should be creating a new record. It does in WP no problem but then gets that error trying to send it to SF.
Thanks for helping me understand!
-
This reply was modified 8 years, 1 month ago by
enils7.
Yes, this is a Salesforce API issue of some kind. That said, I’ve never seen that particular issue, although Salesforce does not always have the most useful error messages.
I notice in your original post that you’re only mapping the email field. What happens if you add more fields, making sure that all required fields are present? For example, at least in our Salesforce, the LastName field is required to create a contact. Usually, Salesforce will return an error to this plugin stating that a required field is missing, but it’s possible that is still the issue but it is not returning it for some reason.
Thread Starter
enils7
(@enils7)
Ah, that makes sense. We had Last Name and Account as required. I removed Account’s requirement but left Last name. Then I added Last name mapping in the plugin along with email and pushed to SF.
I’d like to think this error is ‘progress’ 🙂
I’ll keep messing more tonight, but if this gives you any other ideas, I’m all ears!
URL: https://na73.salesforce.com/services/data/v42.0/sobjects/Contact/tmp_sf_5ad613e585ced3.09629244
Message: Provided external ID field does not exist or is not accessible: tmp_sf_5ad613e585ced3.09629244
Code: 404
(Thanks again for the quick response)
Sometimes that one is a permissions issue. But in this case I’m not sure if it is. You may want to try the Mapping Errors tab in this plugin. When errors occur, it stores a record basically in limbo, and generates a temporary ID. It tries to resolve itself, but sometimes it is unable to do that. I would try deleting the row from there, and then try again to push to Salesforce.
Thread Starter
enils7
(@enils7)
You nailed it! Did exactly that – deleted all old mapping errors which cleared any SF mapping associated with the user, pushed again as a new contact and it worked like a charm!
Thank you for your insight!
