1

I applied a Deterministic case insensitive encryption on contact.name field, And whenever I use it in a WHERE clause of SOQL query, it throws me an Field 'Name' can not be filtered in a query call. I though if you apply Deterministic Encryption to a field you can use it in SOQL Where clause? Need help for this one.

4
  • I'd try synchronizing data (or re-synchronizing if you've done it before) and see if that helps. If the encryption is truly deterministic, it sounds like a bug.
    – identigral
    Commented Jul 11, 2019 at 10:34
  • 3
    I wonder if the issue relates to the fact that Contact.Name is a compound field generated from the (Title,) FirstName, (MiddleName) and LastName values? Could you apply encryption on these fields instead?
    – Phil W
    Commented Jul 11, 2019 at 10:37
  • The weird thing is documentation uses Contact. Name for examples in their soql query for deterministic encryption haha.
    – imajmdf
    Commented Jul 11, 2019 at 10:53
  • I'd contact support - the field is clearly set up to support all three flavors of encryption
    – cropredy
    Commented Jul 11, 2019 at 19:59

1 Answer 1

2

This is expected behavior. When you encrypt contact name we're actually encrypting first name and last name separately. See the linked help article which explains the considerations for deterministic encryption, as it has a section dedicated to this and provides a workaround.

https://help.salesforce.com/articleView?id=security_pe_deterministic_considerations.htm&type=5

1
  • 1
    Yeah , I miss understood this part of Name vs First Name and Last name. thanks a lot
    – imajmdf
    Commented Jul 15, 2019 at 6:44

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .