2024-02-28 - History to Event - Take 2 (new template for change data)¶
Problem¶
The original loading pattern for change data was missing status changes if the rest of the record wasn’t changing - eg if the customer status was changing from active to cancelled then back to active again, the original pattern of comparing the row hash of the record was overlooking the change back to active as the row hash was one we had already seen.
Solution¶
We now use a pattern of comparing the current records row hash with the previous records row hash (lagging record) to identify changes.
Example of the patterns can be seen in our data load patterns overview - https://kitchen.agiledata.io/plumbing-guild/patterns/persisting-data.html
We also now use a point-in-time pattern for joining events to details to correctly pickup the attributes (eg status) of each detail at the point in time that the event occurred
Leverage the Magic¶
We extended our jinga data load templates to incorporate new patterns for loading change data into detail and event tiles.
Last Refreshed¶
Doc Refreshed: 2024-03-03