Update Triggering Logic

Application Scenario

This document describes the update logic of FineBI.

Parent Table and Subtable

If table A is created with data from table B and table C, table B and table C are the parent tables of table A.

Data Lineage shows the relationship between the subtable and the parent table. For details, see Data Lineage.

During global update:

All folders for which During Global Update is set to Update will be updated.

All base tables for which During Folder Update is set to Full-Volume Update All Time or Full-Volume Update Only for the First Time (Incremental Update Hereafter) will be updated.

All sub-datasets for which Update Setting is set to Update With Parent Table will be updated.

All associations affected by the dataset update will be updated.

Update-relied logic (update order):

1. The base table will be updated first.

2. The association between two tables will only be updated after the data in both tables has been updated.

3. The subtable will be updated only after the association between the parent tables used by the sub-dataset and the parent table used by the subtable is updated.

Logic of Updates Triggered by the Single-Subtable Update

1. When a subtable is updated, the system will check all the direct parent tables of the subtable. If it is found that a parent table needs to be updated, the parent table will be automatically added to the update list.

2. The system will check again whether the parent tables of the updated parent tables need to be updated until no update requirement is found.

3. Parent table update will not trigger update of other subtables, but will trigger the update of all associations of the parent table.

4. By default, the system can trigger update of no more than 30 parent tables and their associations. You can modify the maximum number through the parameter SystemOptimizationConfig.maxUpsFatherNum the visualization configuration plugin. For details, see FINE_CONF_ENTITY Visualization Configuration.

Updating Associations Separately

During separate association update in Association Setting:

If one of two associated tables has never been updated, the system will automatically add the never-updated table to the update list when you update the association separately.

The system will check whether the parent table of the table that triggers the update needs to be updated (same as the logic in section "Trigger Logic of the Separate Subtable Update").

Logic of Triggering Excel Table Update

During global update or business package update:

The modification of parameters that need to be calculated will automatically trigger Excel table update to update and re-extract the Excel file.

The parameters to be calculated include Week Start from and Data Type Identification.

The nonexistence of the Excel cache file (T_xxxxx) will trigger Excel table update  to update and re-extract the Excel table itself.

All Excel subtables that have not been updated will be triggered to be updated, while the Excel table itself will not be updated and extracted again. The Excel subtables that have been updated will not be updated again.