2026-10-16 - Choose Change or Event Loading for Landing to History¶
Release¶
AgileData.io - You Know Your Data Best: Override How History Records Are Loaded
When data moves from landing into history, AgileData has to decide what counts as a “new” record. Rows that change over time, such as a customer’s status or an account balance, need every version kept, including a value that changes back to an earlier one. Rows that describe something that happened once, such as a transaction, a reading or a video view, should be loaded once and any re-delivery ignored.
AgileData detects which pattern fits by looking at the shape of your data. That works well most of the time, but shape isn’t meaning. A table of one-off transactions without typical event column names could be treated as changing data, so re-delivered files would load duplicates. A busy daily snapshot could be treated as events, so a record that reverts to an earlier value would be silently skipped.
You can now set this yourself. The Input Table step of a landing to history rule has a new Load Type toggle with three options: Auto, which shows what was detected, Change and Event.
What’s New:
Load Type toggle (Auto / Change / Event) on landing to history rules
Auto mode shows which pattern AgileData has detected, so you can confirm it at a glance
Removing an override returns the rule to automatic detection on the next save
Switching the load type on an existing tile marks it for rebuild, so history is regenerated consistently
What this means for you:
No more duplicate rows from re-delivered event files
No more missed changes when a record returns to an earlier state
Control over a decision that matters most for history, without needing support to step in
Last Refreshed¶
Doc Refreshed: 2026-10-21