The Advanced tab provides task-level overrides for backup and delta change tracking behavior. These settings allow you to tailor data retention and change detection on a per-task basis, overriding the global defaults configured in the tenant settings.
The sections available in this tab depend on the features enabled in Tenant Settings. If neither backups nor delta tracking are enabled globally, this tab will not show any configuration options.
Backup Settings
The Backup settings section is displayed only when the Backups to Keep value in Tenant Settings is set to at least 1. This section lets you control which result tables produced by this task are included in the backup cycle.
Select one of the following options:
•Exclude all results of this task from being backed up
No tables produced by this task will be included in any backup, even if the global backup setting is active. This option is selected by default.
•Include all tables in backups after each task execution
All result tables produced by this task will be backed up automatically after each execution.
•Include only the following tables in the backup
Only the tables you explicitly select will be backed up. When you choose this option, a Backup tables selector appears, showing all result tables associated with this task. Use the selector to add or remove specific tables from the backup list.
|
Note: The table selector only lists tables whose names begin with the task dataset name and excludes tables that are already backup copies (tables whose names end with _Backup_<number>). Tables become available in the selector only after the task has been executed at least once. |
The task-level backup setting takes precedence over the global Backups to Keep count. For example, you can configure the tenant to keep 1 backup globally, while keeping the last 5 runs for a specific critical task by selecting Include all tables in backups after each task execution in combination with an appropriate global backup count, or by selecting specific tables via Include only the following tables in the backup.
Track Changes (Delta Settings)
The Track Changes section is displayed only when the Track data changes automatically option is enabled in Tenant Settings. This section lets you control how delta change tracking is applied to the result tables of this specific task.
For a general introduction to delta change tracking, metadata columns, and API access, see Delta Comparison Feature.
Select one of the following tracking modes:
•Track changes for every table created by this task
Change tracking is active for all result tables produced by this task. This is the default behavior when delta tracking is enabled globally. An Ignore Tables field is also available to exclude specific tables or patterns (for example, entering Inventory* excludes all tables whose names begin with "Inventory"). Wildcards (*) at the end of a pattern are supported.
•Track no changes
Delta change tracking is disabled entirely for this task. No metadata columns will be added to the result tables, and no deletion tracking will occur.
•Define custom rules for change tracking on tables created by this task
Allows fine-grained control over which rows and columns are included in change tracking. When this mode is selected, two additional sections appear:
Row Filters
Row filters define per-table conditions that restrict which rows are included in change tracking. Only rows that match the filter expression for a given table will have their changes tracked.
To add a row filter:
1.In the Add row filter for table field, select a table from the list or type a table name.
2.A filter entry for the selected table is added to the list. Enter the filter expression for that table.
3.Repeat for each table that requires a custom row filter.
If no row filters are defined, change tracking applies to all rows in all tables (subject to the Ignore Tables setting).
Column Behavior Rules
Column behavior rules assign a specific tracking behavior to individual columns of result tables. This lets you designate which columns act as row identifiers and which columns should be excluded from change detection.
The following behaviors are available:
•KEY
Marks the column as the row identifier. This column is used to match rows across task executions when detecting updates and deletions. Assign KEY to the column that uniquely identifies a row in the result table.
•IGNORE
Excludes the column entirely from change detection. Changes to this column will not trigger an update record in the delta tracking history.
•IGNORE_FOR_MD5_HASH
Excludes the column from the MD5 hash-based comparison only. The column is still stored and accessible, but changes to its value alone will not be reflected in the hash-based change detection. Use this for columns with high-frequency volatile data (such as timestamps or counters) that should not trigger a change record.
To add a column behavior rule, click Add rule, then select the target table and column, and choose the desired behavior from the dropdown. Multiple rules can be defined for different columns and tables.
|
Note: Column names become available for selection only after the task has been executed at least once. If no column behavior rules are defined, the system uses the table primary key as the row identifier and includes all columns in hash-based comparison. |