Tasks

Back Next

Case 2. Select the configured path with filter on Account

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 image shows that the data subset filter is applied on the Account object with the account names that start with the letter A. The number of join operations is 4.

Consider that you choose both the relationships Account and ParentAccount__r between Account and Contact objects. The number of join operations to compute the subset with the configured path is four.

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

The image shows the graphical representation of the relationships between Account and Contact objects. The path from Account to Contact through the relationship Account and the path from Contact to Account through the relationship ParentAccount__r are selected.

The task first loads the records from the Account object on which the filter is applied. Then the task traverses through the selected paths from Account to Contact through both the relationships Account and ParentAccount__r. To maintain referential integrity, the task traverses from Contact to Account through both the relationships Account and ParentAccount__r.

The following image shows the selection sequence of the objects:

The image shows the selection sequence for the Account and Contact objects with the filter on the Account object.

Based on the filter applied, the Account object has five rows. From Account to Contact, the Contact object has ten rows with both the relationships Account and ParentAccount__r. From Contact to Account, the Account object has seven rows with the relationships Account and 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 12 rows, the task loads five subset rows that are unique for the Account object from both the relationships. Though the Contact object shows total 10 rows, the task loads seven subset rows that are unique for the Contact object from both the relationships.

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