Knowledge Base Academy Community My Tickets

Home Knowledge Base Academy Community My Tickets

Fabric 6.4

Knowledge Base Sync Methods

Sync Methods

Sync Properties

Sync properties can be defined on an LU schema, LU table, or Table Population level. T A Sync property contains the following settings:

Timeout (sec)	The timeout in seconds for syncing the LUI.
Sync Method	None, Time Interval, Inherited and Decision function.
Parameters	Settings of the selected sync method. For more details see the Sync Methods section below.
Delete Instance if Not Exists	When marked as True, Fabric deletes the LUI if the LUI is not found in the source system. When marked as False (default), the instance is retained in Fabric even if the instance is not found in the source system.

Click for more information about Set Timeout for Sync.

Sync Methods

None

Sync Method	None
Description	Do not sync
Parameters	NA

Time Interval

Sync Method

Time interval.

Description

Synchronization is implemented automatically after each predefined time interval to check if the latest update of the instance in Fabric occurred before the time interval of the specific instance.

· When Yes, data is extracted from the source and reloaded to Fabric.

· If not, the current data in Fabric is used.

Parameters

Perform sync every:

Format = D.HH:MM:SS.

When set to 00:00:00 - if sync mode is force or on - always sync.

Default = 1 day (1:00:00:00).

Decision Function

Sync Method	Decision
Description	Synchronization is implemented according to the Decision function which returns a Boolean (True / False) parameter. If the Decision function returns False, do not sync the object.
Parameters	Decision function: select the Decision function from the Predefined Decision Functions dropdown list.

Inherited

Sync Method

Inherited.

Description

Synchronization of each level inherits the sync rule of its direct parent branch according to the following hierarchy:

· LU table inherits from the LU schema.

· Table Population inherits from the LU table.

Parameters

Click for more information about LU Sync Levels

Truncate Before Sync

The Truncate Before Sync property can be set on an LU table or a Table Population. When Truncate Before Sync = True, whether on the LU table or on one of its populations, the entire LU table is truncated before the related populations are executed for this LU table. Therefore, there is a logical dependence between this setting and the sync mode.

Sync Methods - Use Cases

When is a sync method selected?
None	The source does not change or becomes unavailable and therefore requires a one-time only load. After it is loaded, Fabric becomes the system of record for the data whereby Fabric may get update transactions on the data. For example, add a new payment.
Time Interval	Sync every X times to ensure the data is up to date.
Decision Function	Requires specific logic to check if the data needs to be synced from the source.

EXAMPLES

Sync Method	Example 1	Example 2
None	Load task execution statistics. Once the execution is finished, load its statistics. The statistics are not updated.	Get initial Customer data loaded from the Billing system. Additional payment transactions may then be sent by the Payment Gateway system to update the Payment LUI table for the customer. There is no need to re-load the entire Customer object from the Billing system.
Time Interval	Sync the data every day or every week.	Sync the data every day.
Decision Function	Check the source environment: Do not run a sync on the Production environment. However, if the source environment is a Testing environment, run a sync.	An LU that can be populated by different source systems. Set a different population with different logic for each table and then check the environment on the decision function of each population to decide if the population needs to be executed based on the environment.

Sync Methods

Sync Properties

Sync properties can be defined on an LU schema, LU table, or Table Population level. T A Sync property contains the following settings:

Timeout (sec)	The timeout in seconds for syncing the LUI.
Sync Method	None, Time Interval, Inherited and Decision function.
Parameters	Settings of the selected sync method. For more details see the Sync Methods section below.
Delete Instance if Not Exists	When marked as True, Fabric deletes the LUI if the LUI is not found in the source system. When marked as False (default), the instance is retained in Fabric even if the instance is not found in the source system.

Click for more information about Set Timeout for Sync.

Sync Methods

None

Sync Method	None
Description	Do not sync
Parameters	NA

Time Interval

Sync Method

Time interval.

Description

Synchronization is implemented automatically after each predefined time interval to check if the latest update of the instance in Fabric occurred before the time interval of the specific instance.

· When Yes, data is extracted from the source and reloaded to Fabric.

· If not, the current data in Fabric is used.

Parameters

Perform sync every:

Format = D.HH:MM:SS.

When set to 00:00:00 - if sync mode is force or on - always sync.

Default = 1 day (1:00:00:00).

Decision Function

Sync Method	Decision
Description	Synchronization is implemented according to the Decision function which returns a Boolean (True / False) parameter. If the Decision function returns False, do not sync the object.
Parameters	Decision function: select the Decision function from the Predefined Decision Functions dropdown list.

Inherited

Sync Method

Inherited.

Description

Synchronization of each level inherits the sync rule of its direct parent branch according to the following hierarchy:

· LU table inherits from the LU schema.

· Table Population inherits from the LU table.

Parameters

Click for more information about LU Sync Levels

Truncate Before Sync

Sync Methods - Use Cases

When is a sync method selected?
None	The source does not change or becomes unavailable and therefore requires a one-time only load. After it is loaded, Fabric becomes the system of record for the data whereby Fabric may get update transactions on the data. For example, add a new payment.
Time Interval	Sync every X times to ensure the data is up to date.
Decision Function	Requires specific logic to check if the data needs to be synced from the source.

EXAMPLES

Sync Method	Example 1	Example 2
None	Load task execution statistics. Once the execution is finished, load its statistics. The statistics are not updated.	Get initial Customer data loaded from the Billing system. Additional payment transactions may then be sent by the Payment Gateway system to update the Payment LUI table for the customer. There is no need to re-load the entire Customer object from the Billing system.
Time Interval	Sync the data every day or every week.	Sync the data every day.
Decision Function	Check the source environment: Do not run a sync on the Production environment. However, if the source environment is a Testing environment, run a sync.	An LU that can be populated by different source systems. Set a different population with different logic for each table and then check the environment on the decision function of each population to decide if the population needs to be executed based on the environment.