Tasks > Masking tasks > Data subset use cases for three objects
  

Data subset use cases for three objects

Consider that you selected the Account, Case, and Contact objects in a task. Account is the parent object, and Case and Contact are the child objects of Account. The Contact object is also parent to the Case object. Multipath relationship exists between Account and Case objects.
The task uses the default path to select the records. You can also configure the path to select the records.

Case 1. Default path

The following image shows the default path that the task chooses:
The image shows Account, Case, and Contact objects and the path that the task traverses when you do not configure child records selection.
Based on the default path selection, the task traverses to the Case object directly, and then traverses to the Contact object.
If you apply filter with Account Name equals to Bank of New York, the task marks the default minimal path Account -> Case to traverse through the complete graph. The task selects the Bank of New York account from the Account object and then marks the corresponding two records in the Case object based on the AccountID. The task traverses to the Contact object and selects the corresponding records based on ContactID. To maintain referential integrity, the task selects the additional account Accenture from the Account object.

Case 2. Configured path

The following images shows the path that you configure:
The image shows Account, Case, and Contact objects and the path that the task traverses when you configure child records selection.
If you configure to select the Contact -> Account and Case -> Account paths, the task first traverses to the Contact object and then traverses to the Case object.
If you apply filter with Account Name equals to Bank of New York, the task marks the corresponding ContactID in the Contact object based on the AccountID. For the selected ContactID in the Contact object, the task marks the corresponding Case ID in the Case object.