Data Mask Considerations
When running Data Mask in your sandbox, it’s important to understand how rules and records are handled.
Required Editions
| Available in: Lightning Experience |
| Available in: Professional, Enterprise, Unlimited, and Developer Editions with the Salesforce Data Mask or Data Mask & Seed add-on licenses |
Data in Required Fields Is Missing
All required fields must have data for Data Mask to finish running. A field that changes from optional to required can have data missing. The Data Mask is considered complete in this scenario, but it skips incomplete records.
Bypassing Workflows, Triggers, and Validation Rules
Data Mask bypasses custom workflow rules, triggers, and validation rules created in the org running data masking, including automations from installed managed packages.
Masking Person Accounts
Person Account data resides on two objects, Account and Contact. To mask Person Account record data, you must configure Data Mask to mask the relevant fields wherever that data resides, whether in the Account object, in the Contact object, or in both of these objects.
Data Mask can’t bypass automations on the Contact object when Person Account objects are enabled. Therefore, to avoid the occurrence of save errors, you must manually disable automations.
Masking the User Object
Data Mask can’t edit SFDC Admin, Automated Process, or Integration User records. You see an error message during the mask. Use the Data Filter to exclude them from your policy.
To prevent locking users out of the sandbox, use caution when masking the username field.
Picklists Aren’t a Supported Field Type
Picklist fields such as State and Country aren’t masked when enabling a picklist in the sandbox. You see an error message during the mask.
