Table of Contents

Search

  1. Preface
  2. Data integration tasks
  3. Mapping tasks
  4. Dynamic mapping tasks
  5. Synchronization tasks
  6. Data transfer tasks
  7. Replication tasks
  8. Masking tasks
  9. Masking rules
  10. PowerCenter tasks

Tasks

Tasks

Case 4. Select the configured path with filter on Contact

Case 4. Select the configured path with filter on Contact

Consider that you apply a filter on the Contact object with the condition that the first names start 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 Contact object with the first names that start with the letter A. The number of join operations is 6.
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 selection is six.
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 Contact object on which the filter is applied. To maintain the referential integrity, the task traverses from Contact to Account through both the relationships Account and ParentAccount__r. Then the task traverses from Account to Contact through the configured paths for child records selection with the relationships Account and ParentAccount__r and loads additional records. To maintain referential integrity for the additional records, the task traverses from Contact to Account through both the relationships Account and ParentAccount__r.
The following image shows the sequence in which the task selects the records:
The image shows the selection sequence for the Account and Contact objects with the filter on the Contact object.
Based on the filter applied, the Contact object has 15 rows. From Contact to Account, the Account object has 13 rows through both the relationships Account and ParentAccount__r. From Account to Contact, the Contact object has 16 rows through both the relationships Account and ParentAccount__r. From Contact to Account, the Account object has 17 rows through 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. In this use case, though the Account object shows total 30 rows, the task loads 14 subset rows that are unique for the Account object from both the relationships. Though the Contact object shows total 31 rows, the task loads 15 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:
The image shows the subset statistics for the Account and Contact objects.

0 COMMENTS

We’d like to hear from you!