QUESTION:
We are looking at implementing Salesforce's Shield Platform Encryption and need to know what impact this will have on the DupeBlocker, DemandTools and PeopleImport applications.
ANSWER:
***DupeBlocker***
DupeBlocker can be installed when fields are encrypted using Shield Platform Encryption. However, changes made in Summer '18 required some formula fields in DupeBlocker to be updated to support encryption. Existing users will need to upgrade to version 3.9.8 (or higher), in order to enable encryption on email, phone or name fields.
Note: The duplicate key field will NOT be encrypted at rest, and will contain field data for an encrypted field (if the field was used in the scenario matching rules).
***DemandTools and PeopleImport***
The ability to use encrypted fields in conditions will depend on the chosen encryption scheme (Probabilistic or Deterministic):
Probabilistic:
- Encrypted fields WILL NOT be shown in the list of fields to base a condition on
- Cannot be used in where clauses (i.e. cannot be filtered on)
Deterministic (new in Salesforce Summer '18):
- Encrypted fields WILL be shown in the list of fields to base a condition on
- Only the = and != operators will work
- If a different operator is selected (e.g. starts with, contains) an INVALID_QUERY_FILTER_OPERATOR error will be displayed in the UI when attempting to get results
- Only the = and != operators will work
Note: Filtering issues are NOT unique to DemandTools or PeopleImport. You will have the same problem attempting to filter on encrypted fields in the Salesforce Data Loader and elsewhere.
Please refer to Salesforce's Help Documentation for more information regarding Platform Encryption:
Strengthen Your Data's Security with Shield Platform Encryption
Note: Since Salesforce can change how encryption works at any time we highly recommend that users do their own tests in a sandbox environment with our tools as we do not guarantee that we have uncovered all the possible issues.