While the Data Mask package can be installed and configured in your production org, data
masking jobs only run in sandbox orgs. That way, the data in the production org isn’t accidentally
masked. When the configuration is complete, you can mask your sandbox data. Run the mask each time
you want to replace or delete the data in your sandbox. Or, set the mask to automatically run each
time you refresh your sandbox.
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
Note This content relates to Salesforce Data Mask. Read
about Accelerate and Anonymize in Own from Salesforce.
From your Configuration tab in your sandbox, click Run and then
Confirm.
To monitor the progress of a masking run, click the Jobs tab and
then the mask name link. From the Affected Records section, you can choose to wrap or clip the
text for any of the fields from the dropdown. To open another masking run or investigate any
errors, close the tab.
Summary Items
Description
Scheduled or Summary
The date and time that the mask runs. For a manual mask run, it shows a summary,
otherwise it shows the scheduled run time. The summary explains the job status. For
example, in the queue, it identifies whether a job is completed. It shows the
configuration from where the job was created. If a configuration is deleted after a job
runs, it displays [Deleted].
[Object Name]
The status of the field now being masked. For example, for a contact, you see
loading records, acting on records, and clean up.
Jobs Completed
A green check mark indicates that the masking job is complete.
Affected Records (X)
If any of the records are affected during the mask run, you see the object name,
number matched, deleted, masked, or errors. By closing the dialog, you can view another
mask job or investigate any errors from the Failures section.
Errors
It shows the object name, its record id, the type of error, and any associated
message.
To verify that records are masked properly, manually spot-check your sandbox data. Then you
can grant more users access to the sandbox.
The masking process runs asynchronously and can take several hours for large sandboxes. Data
Mask bypasses these automations during execution, including objects from Managed Packages.
Triggers
Workflow Rules
Validation Rules
Flows
Feed Tracking
Data Mask also deletes all Field History Tracking associated with the Object when the masking
job is complete.
If the Email Deliverability setting is set to All Emails, you receive an email when the job
completes.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.