Hi Jonathan,
What this mean for the Salesforce ID? tmp_sf_5f20781542c981.30446982
This means the Salesforce object was not yet created. Usually this happens in the middle while the plugin is still processing, and then the plugin updates the value with the correct ID once it’s finished. If it does not get updated, this means there has been an error. You can check the plugin’s error logs, or your server’s error logs, to see what that error might be.
Hi Jonathan,
Test Connect Salesforce ID 00Q3a00000qUaWM
https://bankrollio.my.salesforce.com/00Q3a00000qUaWM
The lead was created in Salesforce, I mapping based off of the email address.
Salesforce Id tmp_sf_5f247a13f1efd3.68467845 Edit | Delete
Last Sync Message Mapping object updated via function: salesforce_push_sync_rest
Last Sync Action push
Last Sync Status success
Last Sync 2020-07-31 20:28:58
Actions Push to Salesforce Pull from Salesforce
Well, it’s possible that this plugin isn’t going to work for you. I don’t have the capacity to give this kind of individualized support at this time, in any case.
I created another User and once again TMP ID for Salesforce. If I click the TMP Id it takes me to salesforce and says record not found. Then I when refresh the user in wordpress it updates to the correct Salesforce Id. But I cant do that manually all the time.
Hi There @jonathanstegall
I’m experiencing exactly the same problem here. I have created one simple feed from WP to SF that includes firstname, surname, company, email and a few other fields.
The Mapping Error appears as follows:
Type WordPress ID WordPress Object Type Salesforce ID Created Date/Time Actions
Pull from Salesforce 1192 user tmp_sf_5f5a1a97e14e81.84140670 2020-09-10 1:22:47pm
There don’t appear to be any actions, or indication of what the error might be.
Looking at the record itself, I see the following:
Salesforce Id tmp_sf_5f5a1a97e14e81.84140670
Last Sync Message Mapping object updated via function: salesforce_push_sync_rest
Last Sync Action push
Last Sync Status success
Last Sync 2020-09-10 13:22:48
Which implies the push was successful but no record appears in Salesforce.
I have tried deleting the error message and pushing again, which does then push the record.
Are you able to shed any light on this as it appears to be a common issue.
Appreciated
Paul
@tamedmedia The issue you’re seeing is that the plugin was unable to save data.
Here’s the relevant part of how the plugin works:
1. Before it pushes data from WordPress to Salesforce, or pulls it from Salesforce to WordPress, it creates a temporary ID and saves it.
2. If the data save is correct, it will always replace that temporary ID with the object ID that it has created. So it’ll be a WordPress object ID if it was a pull, or a Salesforce object ID if it was a push.
In your case, it seems to be saying it was unable to pull from Salesforce to WordPress. You can push it too, but if that works, it’s because it created a new record in Salesforce.
The plugin should always create error logs when data isn’t saved, if there’s an error message from Salesforce or from WordPress. You can read about that in the documentation here: https://github.com/MinnPost/object-sync-for-salesforce/blob/master/docs/logging.md
Hi @jonathanstegall – thanks for the prompt response.
Yes, that’s what’s a little confusing because the one mapfield I setup only pushes WP user data to SF, as a new user, and has no instruction to pull from SF.
I was confused by the error, which started with Type = Pull from Salesforce.
This is a little confusing.
Any thoughts on that?
Appreciated
Paul
Not really, you might want to delete the fieldmap and try again.
Thanks @jonathanstegall for the info on logs. I now see where to go for the detail…
So here are a couple of the errors in more detail. What does this suggest? Something related to caching?
DEBUG #1
Debug: on Salesforce API HTTP Request to URL: https://fillmed.my.salesforce.com/services/data/v49.0/sobjects/Lead/tmp_sf_5f5a61a0d54fb6.37301986.
Array
(
[code] => 404
[data] => Array
(
[0] => Array
(
[errorCode] => NOT_FOUND
[message] => Provided external ID field does not exist or is not accessible: tmp_sf_5f5a61a0d54fb6.37301986
)
)
[from_cache] =>
[cached] =>
[is_redo] =>
)
ERROR #1
Error: 404: on Salesforce HTTP request
<p>URL: https://fillmed.my.salesforce.com/services/data/v49.0/sobjects/Lead/tmp_sf_5f5a61a0d54fb6.37301986</p><p>Message: Provided external ID field does not exist or is not accessible: tmp_sf_5f5a61a0d54fb6.37301986</p><p>Code: 404
DEBUG #2
Debug: on Salesforce API HTTP Request to URL: https://fillmed.my.salesforce.com/services/data/v49.0/sobjects/Lead/tmp_sf_5f5a61a0d54fb6.37301986.
<p>URL: https://fillmed.my.salesforce.com/services/data/v49.0/sobjects/Lead/tmp_sf_5f5a61a0d54fb6.37301986</p><p>Message: Provided external ID field does not exist or is not accessible: tmp_sf_5f5a61a0d54fb6.37301986</p><p>Code: 404
ERROR #2
Error: 404: on Salesforce HTTP request
URL: https://fillmed.my.salesforce.com/services/data/v49.0/sobjects/Lead/tmp_sf_5f5a61a0d54fb6.37301986 Message: Provided external ID field does not exist or is not accessible: tmp_sf_5f5a61a0d54fb6.37301986 Code: 404
No. As I mentioned earlier, the plugin generates a temporary ID. That is what all these errors are about; the Salesforce API is returning errors because that ID does not exist.
It may be that there’s another error before any of these that is the actual, initial error. These are likely to keep happening because the temporary ID is not a real object ID.
OK, so does the tmp ID need to be created if the user is new and simply needs to be pushed from WP to SF as a new Lead?
No. If you are pushing from WP to SF and there isn’t a problem before the push, the Salesforce API will create the new lead for you. Salesforce generates its own unique IDs, you can’t generate those for it.
OK, thanks again @jonathanstegall
In my case, the fieldmap is only sending to Salesforce from WP. So it should just send and add, right? Wondering why it’s not…?
Yes, it should. If the Salesforce API returned an error message, the plugin should have tried to log it as well, but if you have a lot of log messages it might be hard to find the original one.
