Consider that you apply a filter on the Account object with the condition that the account name starts with the letter A.

The following image shows the data subset filter criteria that you can configure:

The task traverses the default path from Account to Contact through the relationship Account. The number of join operations to compute the subset with the default path selection is two.

The following image shows the graphical representation of the relationship between Account and Contact objects:

The task first loads the records from the Account object on which the filter is applied. Then the task traverses through the default path from Account to Contact through the relationship Account and loads the records. To maintain referential integrity, the task traverses from Contact to Account through the relationship ParentAccount__r.

The following image shows the sequence in which the task selects the records:

Based on the filter applied, the Account object has four rows. From Account to Contact, the Contact object has five rows through the relationship Account. From Contact to Account, the Account object has three rows through the relationship ParentAccount__r.

To view the number of subset rows, you estimate the subset. If there are common records from multiple join operations, the task updates the records. If there are new records, the task adds the subset rows. In this use case, though the Account object shows total seven rows, the task loads four subset rows that are unique for the Account object from all the relationships. The task loads five subset rows for the Contact object.

The following image shows the subset statistics that you can estimate in a task: