How are encrypted fields (Classic Encryption) handled by DupeBlocker?

QUESTION:

How are encrypted fields handled by DupeBlocker?

ANSWER:

• Matching on encrypted fields:
  • DupeBlocker can match on fields that are encrypted.
  • The duplicate key has the actual data in it vs. the encrypted data.
  • The key field on DupeBlocker Potential Duplicate records will show the data, and it will not be encrypted in the key.
    • Since the key is a required field on the DupeBlocker Potential Duplicate object there is no way to control the value entered into the key field.  
    • The Duplicate Key field can be hidden using field level security.

Note:  User may also want to review the following solution: Are Validity Tools Compatible with Shield Platform Encryption?

 ***Below is information on encrypted field use for clients also using DemandTools and PeopleImport*** 

• Matching on encrypted fields:
  • DemandTools & PeopleImport
    • Users that have the "View Encrypted Data" permission on their Salesforce profile will be able to use an encrypted field in their matching.
    • Depending on the mask chosen for the encrypted field, other users may be able to select the encrypted field for matching. 
    • DemandTools analyses the mask NOT the data behind the mask, if the enitre field is masked, every record with this field populated with the same number of characters will be returned as a match
• Using Encrypted Fields in a Where Clause:
  • DemandTools & PeopleImport 
    • Encrypted fields CANNOT be used in where clauses, i.e. cannot be filtered on, regardless of having "View Encrypted Data" permission.
      • Note:  This is NOT unique to DemandTools/PeopleImport, you will have the same problem attempting to filter on encrypted fields in the Salesforce Data Loader and elsewhere. 
• Updating a Field with Data from an Encrypted Field:
  • DemandTools 
    • ONLY users with "View Encrypted Data" should attempt to update a field with data directly from an encrypted field (i.e. MassImpact "Update Value" using the "Field Tab"), otherwise the mask characters will be populated in the field being updated vs. the actual date.