Sync Method Levels
What Are Sync Method Levels?
Sync properties can be defined on LU schema, LU table or Table Population levels. By default, LU tables, Table Population objects and Enrichment functions inherit the sync properties defined for the LU schema. The sync properties of an LU schema can be overridden, as follows:
- Setting sync properties on the LU Table. By default, the related Table Population objects and the Enrichment functions attached to the LU table inherit the sync properties of the LU table.
- Setting sync properties on each Table Population object.
Overriding Sync Properties in an LU Schema - Use Cases
You may need to override the LU schema's sync properties on LU tables or Table Populations that require specific handling. The following table describes use cases for overriding the sync properties on each object:
- LU Table.
- Table Population.
|
LU Table Use Case |
Table Population Use Case |
|
Override the LU schema's sync properties and set specific sync properties on an LU table in either of the following cases:
For example, an Enrichment function of an LU table initiates a purging (cleaning) process on a DB table to remove old data from the DB table. Since the Enrichment function needs to be executed frequently, set a specific sync method on the related LU table. |
The table has several populations where each population requires a different sync method. Example 1 When migrating customers from two different Billing systems (System A and System B) into Fabric, both systems are migrated into the same Billing LU. Each LU table has two table populations:
When getting Customer 1 data from System A, Fabric only needs to execute the sync on Population 1. When getting Customer 2 data from System B, Fabric only needs to execute the sync on Population 2. Therefore, set a Decision function for each population to check the source system for each execution and return True or False accordingly. Example 2: In the Table Population of the CUSTOMER LU table set the CUSTOMER_TYPE Global variable according to the predefined mapping logic. The INVOICE LU table has two table populations:
Therefore, set a Decision function for each population to check the CUSTOMER_TYPE Global variable to execute the correct Table Population based on the customer type of each LUI. |
Sync Method Levels
What Are Sync Method Levels?
Sync properties can be defined on LU schema, LU table or Table Population levels. By default, LU tables, Table Population objects and Enrichment functions inherit the sync properties defined for the LU schema. The sync properties of an LU schema can be overridden, as follows:
- Setting sync properties on the LU Table. By default, the related Table Population objects and the Enrichment functions attached to the LU table inherit the sync properties of the LU table.
- Setting sync properties on each Table Population object.
Overriding Sync Properties in an LU Schema - Use Cases
You may need to override the LU schema's sync properties on LU tables or Table Populations that require specific handling. The following table describes use cases for overriding the sync properties on each object:
- LU Table.
- Table Population.
|
LU Table Use Case |
Table Population Use Case |
|
Override the LU schema's sync properties and set specific sync properties on an LU table in either of the following cases:
For example, an Enrichment function of an LU table initiates a purging (cleaning) process on a DB table to remove old data from the DB table. Since the Enrichment function needs to be executed frequently, set a specific sync method on the related LU table. |
The table has several populations where each population requires a different sync method. Example 1 When migrating customers from two different Billing systems (System A and System B) into Fabric, both systems are migrated into the same Billing LU. Each LU table has two table populations:
When getting Customer 1 data from System A, Fabric only needs to execute the sync on Population 1. When getting Customer 2 data from System B, Fabric only needs to execute the sync on Population 2. Therefore, set a Decision function for each population to check the source system for each execution and return True or False accordingly. Example 2: In the Table Population of the CUSTOMER LU table set the CUSTOMER_TYPE Global variable according to the predefined mapping logic. The INVOICE LU table has two table populations:
Therefore, set a Decision function for each population to check the CUSTOMER_TYPE Global variable to execute the correct Table Population based on the customer type of each LUI. |
