To reproduce the error (V47), you need
- at least 200,000 Contacts with
Contact.Email populated and encryption sync'd (I used 225,000 with 10,000 having
- 2 Contacts with same email address
- Email-to-case enabled
- Send email from email address represented on 2 Contacts
Contact.Email encrypted Contacts w/ same Email Email-to-Case Result
----------------------- ---------------------- --------------------
Deterministic case-insensitive 2 SOQL non-selective exception
Deterministic case-sensitive 2 Success, no error; case created
So, since SFDC stores email addresses for
Contact.Email always in lowercase, a viable workaround is the following:
- Use Deterministic (Case Sensitive) encryption on
Adjust your SOQL queries to always lowercase the filtering emailAddress(es). For example (assumes
someVbl is non-Null):
[SELECT Id, Name FROM Contact WHERE Email = :someVbl.toLowerCase()];
UPDATE From Support/R&D 2019-12-03
In short, they (R&D) indicated the documentation on this needs to be clarified. The relevant section is at the bottom of the considerations for Deterministic:
Case-insensitive deterministic encryption supports standard indexes on email fields on the Contact and Lead objects, and the Email Message—Relation field. However, you might see slower performance on these fields when they’re encrypted with the case-insensitive deterministic scheme.
Because we say indexes are 'supported' but what we really mean is 'we allow such indexes to exist and do not block encryption, but the indexes do not function as expected.' If this seems like a poor distinction, that's because it is, at least now. Originally we could not support case-insensitive encryption on these fields at all because of the presence of an index that we could not modify. Subsequently, we figured out how to let the index continue to exist and not prevent case-insensitive encryption, but we have not yet been able to make the index actually useful.
A proper restatement would be something like: EmailMessageRelation fields, Contact.Email, and Lead.Email may all be encrypted with case-insensitive deterministic encryption, but doing so will prevent the use of Salesforce standard indexes, which could impact performance on your queries.
... They recommend switching to case sensitive encryption for Contact.Email though, so it fully supports the index that is needed due to the record count.