I work for a financial institution and I need to be able to encrypt contact names, but Shield does not allow encryption of standard name fields. Is best practice just to create custom name fields to get around this? Does this cause issues elsewhere?
Also, I read on Salesforce documentation: When you encrypt the Name field, enhanced lookups are automatically enabled. Enhanced lookups improve the user’s experience by searching only through records that have been looked up recently, and not all existing records. Switching to enhanced lookups is a one-way change. You can’t go back to standard lookups, even if you disable encryption.
I'm confused about this, because why would someone want to only search records that have been looked up recently? If one of my users needs to search for a record that hasn't been touched in awhile, how would they find it?
1 answer
Ashley,
Salesforce automatically HTML encodes any values and merge fields placed in HTML context. This includes all standard functionality, as well as Visualforce pages and components.
Please check it:
https://trailhead.salesforce.com/content/learn/modules/secdev_injection_vulnerabilities?trailmix_creator_id=strailhead&trailmix_slug=prepare-for-your-salesforce-platform-developer-i-credential
