Nth Level RTBF/De-identification

  • Nth level de-identification allows you to de-identify/delete any number of records attached to the objects in the hierarchy mapped.
  • Up to Nth levels of the hierarchy of objects can be mapped.
  • To create the mapping for  Nth level de-identification, click on the “Add” button on the RTBF/De-identification tile.
  • Refer to the RTBF/De-identification Mappings article to create the mapping for a single object(Level 1).
  • A child object dropdown field will appear, select the child object (which will be on level 2 ). Click on the add child button. A Level 2 object will be added.
  • Users can also add the filter field from the picklist, on the basis of this filter records will be selected. Make sure that the filter field that user going to suer should be of  data type boolean.
  • Here Account is Level 1 object and Contact is Level 2 object.
  • To add the fields in the mapping of the Level2 object, “Contact” in this example, click on the Contact and add the fields in the mapping. Refer to the RTBF/De-identification Mappings article to check how to add fields in the mapping.
  • To add a Level 3 object user can click on the “Add Child Object” button that is next to the Level 2 object.

Let’s add the Case object as a Level 3 object and CaseComment as a Level 4 object.


After adding Case and CaseComment objects, the mapping will look like the below screenshot.

  •  Likewise, users can add as many objects till the Nth Level and also can add as many objects in each level. For example in this case Account object can have Contact and Asset both the object on Level 2 as shown in the below screenshot.

Once object mapping is ready, users can add fields to respective objects by clicking on the link of each object to perform Nth Level de-identification. 

  • Once the mapping is ready with the fields then go to the list of mapping and mark it as “set as default”.
  • Now navigate to the case to create a new case to process Nth Level de-identification.
  • Select “DSAR – De-identification” and click next.
  • In the Data Subject field enter the salesforce ID of the parent Record(Level 1 object).
  • Save the case
  • Go to the “Data subject records” related list.
  • Click on the “Populate Data Subject” button.
  • Background scripts will run and all level records related to the Account record will show up in the related list.

Note – In the case of the CC 2.29 version and onward RTBF feature allows users to select the mapping before populating the data.

  • Go to the “Data subject records” related list.
  • Click on the “Populate Data Subject” button, After that User can select the RTBF mappings of a particular object.


  • Select the Mapping as per the business use case. In this case, there are two Mappings


  • After Selecting the mapping, click on the Select button
  • Status is “Awaiting Processing” as the de-identification is yet to be processed.
  • Click on the down arrow near the “Populate data Subject” button and click on the “Process Records” button.
  • Now the status has changed to “Processed”.

    Note: If org is upgraded from 2.19 to 2.20 version of Cloud Compliance then make sure that the “Processed” value is added in the “DSAR Status” picklist field on Case object. Also, version 2.26 and below do not support Nth Level RTBF de-identification.
  • Now users can check the deidentified records according to the mapping.

Note: In a similar way users can de-identify any records of any object by mapping them in the hierarchy.

Powered by BetterDocs