DataMasker Deployment

Overview

In the Data Masker application, the user needs to create the Configuration in which Object Mapping and Field Mapping will be added. Users can also create their own patterns with different data types to use for the masking process. This document showcases how the Configurations along with Object Mapping, Field Mapping, and patterns can be transferred from one org to another in order to efficiently migrate data from sandbox to production.


Process Summary

The first step of the data migration process is to extract the CSV files from the source org that contains the mapping data. Extraction can effortlessly be done using Workbench. When the CSV files are ready, these files need to be pushed into the destination org using Workbench. We illustrate this process in detail, below.

This document should be used only as a reference guide as every Org is different and has its unique objects and structure.


Prerequisites

Before starting the Data Migration process, the user needs to create a custom field (data type – Text) with the name “External Id” on the objects i.e. ‘Configurations’, ‘Object Masking’, and ‘Patterns’ in the destination Org. This custom field should be of type ‘Text’, Case Sensitive, and ‘Unique Record Identifier from an external system’.

18.png


Solution Steps – 

Data migration for Data Masker 

Total Objects- 4

  • Configuration
  • Object Masking
  • Pattern
  • Field Masking

1. Configuration

API Name : pcldm__Configuration__c

To create a CSV file, the workbench SOQL for Configuration should be as follows –

SELECT Id,Name,pcldm__Attachments_Files__c,pcldm__Case_Comments__c,pcldm__Chatter__c,pcldm__Description__c,pcldm__Emails__c,pcldm__Events__c,pcldm__Field_History__c,pcldm__Is_Sandbox__c,pcldm__Notes__c,pcldm__Notify_User__c,pcldm__Select_Masking_Type__c,pcldm__Show_Advance_Configurations__c,pcldm__Tasks__c,pcldm__User_Email_ids__c FROM pcldm__Configuration__c

Push the CSV file in Destination org using Workbench. 

Click on Data -> Insert then Select the object and CSV file that needs to be pushed in a destination.

Map Fields

  • Map ‘External_Id__c’ with ‘Id’
19.png

2.Object Masking

API Name : pcldm__Object_Masking__c

To create a CSV file, the workbench SOQL for Object Masking should be as follows –

SELECT Id,Name,pcldm__Active__c,pcldm__Batch_Size__c,pcldm__Configuration__c,pcldm__Count_of_Field_Masking__c,pcldm__External_Id__c,pcldm__Filter_Criteria__c,pcldm__Group__c,pcldm__Last_Runtime__c,pcldm__Object_API__c,pcldm__Object_Label__c,pcldm__Sequence__c,pcldm__Serial_Mode__c,pcldm__Use_Bulk_Api__c,RecordTypeId FROM pcldm__Object_Masking__c

Push the CSV file in Destination org using Workbench. 

Click on Data -> Insert then Select the object and CSV file that needs to be pushed to a destination.

Map Fields

  • Map ‘External_Id__c’ with ‘Id’
  • ‘pcldm__Configuration__c’ with Smart Look Field i.e ‘pcldm__Configuration__c.External_Id__c’.

Note– User needs to change the RecordType Id in the CSV for Mask and Delete record type before inserting from the workbench.

20.png

3. Pattern

API Name : pcldm__Pattern__c

To create a CSV file, the workbench SOQL for Pattern should be as follows –

SELECT Id,Name,pcldm__Data_Type__c,pcldm__Preview__c,pcldm__Type__c,pcldm__Value__c,RecordTypeId FROM pcldm__Pattern__c

Push the CSV file in Destination org using Workbench.

Map Fields

  • Map ‘External_Id__c’ with ‘Id’

Note- Data Masker Application comes with some sample pattern records after post-installation. To avoid duplication of Pattern records from source org to destination org user can delete the pattern records from the destination org which patterns are already created by post-installation and can insert the fresh patterns from the source org.

Note– User needs to change the RecordType Id in the CSV for List and Regex record type before inserting from the workbench.

24.png

4. Field Masking

API Name : pcldm__Field_Masking__c

  To create a CSV file, the workbench SOQL for Field Masking should be as follows –

SELECT Id,Name,pcldm__Action__c,pcldm__Active__c,pcldm__External_Id__c,pcldm__Field_API__c,pcldm__Field_Label__c,pcldm__Field_Type__c,pcldm__Further_Action__c,pcldm__ObjectExternalId__c,pcldm__Object_Masking__c,pcldm__Pattern__c,pcldm__Value__c FROM pcldm__Field_Masking__c

Push the CSV file in Destination org using Workbench.

Map Fields

  • ‘pcldm__Object_Masking__c’ with Smart Look Field i.e ‘pcldm__Object_Masking__c.External_Id__c’.
  • ‘pcldm__Pattern__c’ with Smart Look Field i.e ‘pcldm__Pattern__c.External_Id’.

Note – While inserting the field mapping user needs to confirm the value of the field with the data type Date/time is in the format i.e ‘YYYY-MM-DD HH:MM: SS’, if it has been added into the Field Mapping.

The below screenshot shows the first two mapping fields –

field masking.png

The one below shows the third mapping field –

MicrosoftTeams-image (3).png

Now users can check into the Configuration tab in the Data Masker application. The mapping will have been migrated from source org to destination org. 

Powered by BetterDocs