Issues with Salesforce Upsert Record: Key not found error when selecting table

Gregory G. · 2024-02-27T20:35:23.698826+00:00

Hey folks - when I try to Salesforce Upsert Record and select a table it just fails. Says “Key not found” but the column doesn’t have any other options.

Clay T.

APP

·

Hey hey! Can you drop the URL for your table here? (if applicable) 🫶 Don't worry, only admins will be able to open your table 😉

Gregory G.

·

This fast? Are you serious 😂

Gregory G.

·

https://app.clay.com/workspaces/200786/tables/t_40LARxQyMJoX/views/gv_IRYqF31sb4i6##

Gregory G.

·

Ohh I see it’s a bot - fair play anyway!

Clay T.

APP

·

Hey there Gregory thanks for reaching out. Taking a look.

Clay T.

APP

·

Hey there Gregory sorry for the delay, did some digging around to find what was going on and so the issue here is that Salesforce Upserts, in general, require a field in Salesforce to be marked as an external ID. According to the key you’re using in Clay, no fields in your Salesforce organization are marked as an externalID, so you can’t actually run upserts because no fields load for the upsert key.“ExternalID” is a salesforce setting that says “this field can be used to dedupe salesforce records, but its values come from another source”We can definitely make changes to enable this in our regular lookups, as mentioned in this thread, but the quickest win here would be to mark a field in salesforce as an external ID and then try again

Gregory G.

·

Do you have a recommendation for what to use as external id?

Gregory G.

·

I.e person’s email or internal Clay UUID

Clay T.

APP

·

Sorry for the delay, a person's email would work best, you would want it to be a data point that most leads are likely to have.

9 comments