Error: 404: on Salesforce HTTP request

This error means that the Salesforce record doesn’t exist at the time the plugin is trying to update it. This plugin creates a temporary ID before a new record is created, and then when it is, it puts in the actual ID.

Usually there is another error log that tells you what prevented the record from being created.

Hi Jonathan,

Thank you for your prompt reply.

I am trying to update an existing salesforce lead with wordpress. I’ve mapped all the required fields and this email already exists in my salesforce lead record so I’m not sure why the plugin is unable to match them up.

I received three error logs trying to do this, including:

1. Error: 404: on Salesforce HTTP request
2. Error: Update Salesforce Lead tmp_sf_5f4caf258f6e09.98201348 (WordPress user with ID of 689), with a message saying “Provided external ID field does not exist or is not accessible: tmp_sf_5f4caf258f6e09.98201348”
3. Error: 404: on Salesforce HTTP request

Okay, I think I see what you mean. To start, this plugin does not work with pre-existing data unless there’s already an object map.

That is, if you don’t have a row in the database that connects the correct ID for the Salesforce lead with the ID for the WordPress user, it will not sync. It seems like the plugin is trying to update a record that doesn’t exist. That’s why the first log entry is a 404 and the second is a temporary ID.

This plugin technically doesn’t, by default, work with any data that existed before it was installed. We’ve tried to articulate this in the documentation. You can possibly get around this a little bit by doing an import, if you can generate the JSON that it requires. There’s some info about this in the documentation here: https://github.com/MinnPost/object-sync-for-salesforce/blob/master/docs/import-export.md

The import feature is maybe not ideal for what you want, because you’d have to export a working object map structure and then replace it with the details for the pre-existing data. It’s possible that it would work though.

I seem to be able to update this record just fine after deleting the mapping error for it… Does this mean the plugin successfully mapped the objects?

Log:
Success: Upsert Salesforce Lead 00Q7F00000V6bDFUAZ (WordPress user with ID of 689).

Also could you clarify the difference between Upsert and Update? Does the former simply mean the initial sync and the latter is any updates following?

Yes, that means it successfully mapped them.

The short answer for upsert vs update is that upsert will check if the object already exists. If it does not it will create it. If it does, it will update it.

The match comes from whatever the prematch fields are in your setup. So if you’re matching by email, it would check to see if a record already exists with that email and it would create a new one if not.

My guess is that in your case it has created a new lead, but I can’t know that for sure.

I see. Thanks Jonathan.

My prematch field is email, and it seems to actually updated the existing email in my salesforce leads rather than creating a new one.

I guess another question would be whether the plugin is able to automatically check the mapping error and update the record in salesforce accordingly without having to manually delete the mapping error for every object match?

Also does the plugin try to re-run the error sync automatically?

Currently, if there’s a mapping error the plugin will stop running that item until the error it gets deleted.

As far as automatic syncs, the plugin runs – depending on your settings – when a record is created, updated, or deleted in either system. It doesn’t do anything unless data is modified, in other words.

I’ve been looking into the json import/export and I think that this might be what we need to get do in order to get the plugin working the way we want it to.

We’re not so advanced with our web development knowledge though, do you happen to know someone who we can consult with if we were to start this project?

Well, I believe that an agency in Minneapolis called Software for Good has worked with this plugin in the past, although I don’t have firsthand knowledge of what they’ve done with it. My guess is that they are better suited for large projects, but you could certainly investigate.

If you just need help getting a JSON import, I think it probably doesn’t matter if you choose a consultant that has experience with this specific plugin.

But here’s the advice I would offer: make sure the plugin works with some sample data before you do any work on the import/export, especially if it involves hiring a consultant. Then make sure it works in a test environment, like a sandbox or whatever, before you put it on production.

For more detail, I mean to make sure the plugin works with all of the data requirements you have. You might want to create some new records and make sure all of the fields get updated to your needs, or whatever the case may be. This way you can make sure the plugin is actually capable of doing what you need before you spend money on it.

I say that because sometimes there are data structures or other third party plugins and they don’t work with this one without more development work, which can get pricey.

• This reply was modified 4 years, 6 months ago by Jonathan Stegall. Reason: clarification

@danitaphaopat

This plugin is a solid performer and works as advertised. Recently we used it to sync 130,000 users to Contacts and several custom post type for events and registrations. It keeps on working.

Jonathan is providing sound advice regarding making sure the plugin works with your WordPress environment before importing and syncing production. If you have access to a copy of your WP site for test and a Salesforce sandbox it works best.

Syncing past user data to leads/contacts is a common task for onboarding a new WordPress / Salesforce. This should happen after all data is mapped and tested on test/sandbox.