Add Tracking

Tracking records changes in the data source between two cube refresh tasks and processes only the differences during the next run. This improves refresh performance when only a subset of data changes between loads, rather than reloading all records.

If one data source in the cube does not have tracking enabled while others do, the system recalculates all rows from that source in the cube, based on the cube's history table. If the combined size of data sources with and without tracking is large, it can be faster to perform a full Load All instead of a refresh.

When to track changes

• Improving refresh performance: Track only a small subset of data that changes regularly to shorten refresh times.
• Reducing system load: Avoid reloading unchanged records, minimizing resource usage.
• Synchronizing data updates: Align closely with changes in source data.

Tracking types

Tracking type	Description
Trigger	Tracking method that uses database triggers to capture changes based on key values.
Date	Tracking method that uses date‑time fields to identify records that changed since the last update.

Make the cube editable

1. In the Administration page, select OLAP Manager from the sidebar.
2. In the cube list, select the cube where you want to configure tracking.
3. Clear the In Production checkbox.
4. Click Save.

Add a tracking

Trigger tracking type

Field	Description
Tracking key	Table and field in the data source database to track. The table must be part of the data source definition, but the field does not need to be selected as a dimension or measure.
Tracking mappings	Associations between tracking keys and table fields. This is useful for data source designs that use SQL views without triggers — mapping ensures the tracking key matches the appropriate field from the data source.

note

Trigger tracking is not available for Snowflake data sources.

1. In the Options panel on the right, click the General icon.
2. Select Tracking.
   Or right-click the Workspace and select Tracking.
3. Select Trigger.
4. In Tracking Keys, click Add, then select a table and its corresponding field from the drop‑down lists.
5. In Tracking Mappings, click Add to define the mapping.
6. Double-click a data source table from the list.
7. Expand the table and map each field to its corresponding tracking key field.
8. Click Confirm.

Date tracking type

Field	Description
Primary keys	Unique fields identifying records to update. If any record with the same key changes after the last refresh, all records with that key are updated. Example: Invoice Number, or Invoice Number + Invoice Line.
Date fields to track	Update‑date fields used to detect changes. Multiple date fields from different tables can be tracked — if any date is more recent than the last refresh, related records (based on the primary key) are updated. Example: Track DateLastChange in both InvoiceHeader and InvoiceDetail; if either changes, the update runs correctly.

1. In the Options panel on the right, click the General icon.
2. Select Tracking.
   Or right-click the Workspace and select Tracking.
3. Select Date.
4. In Primary keys, click Add, then select a table and its primary key field from the drop‑down lists.
5. In Date fields to track, click Add.
6. Select the appropriate data type (Date or DateTime).
7. Click the pencil icon to add a calculation if needed.
8. Click Confirm.