I am looking to use an encrypted field as an external ID for the upsert function. As long as the user running the upsert has read access, the fact that it ID for the upser is encrypted shouldn't matter, correct? I want to make sure that when I try to upsert, it wouldn't see an encrypted value, as compared to the text value.

For example, if I wanted to encrypt last name using case-insensitive encryption. Then, I wanted to upsert based on last name, would it see 'Smith' to perform the upsert? OR would it see the encrypted value?



I'm assuming you're using Shield Platform Encryption?


"To encrypt custom fields that have the Unique or External ID attribute, you can only use deterministic encryption".


This article is mainly focused on querying and finding the data using, like you mentioned, the non-encrypted value. This would apply in the same way for dataloader. You should be able to use the non-encrypted value in an upsert to match the records and upsert.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.