Update transformations without resyncing historical data
New Option for Transformation Processing
Great news!
Narrator has added support for updating transformations without resyncing the historical data.
Uncheck the checkbox in the validation flow to update the transformation with resyncing the data
Sometimes you don't want a full historical re-sync
By default, all historical data is resynced when transformations are pushed to production. This is important when the activity definition changes, but sometimes you don't want a full historical re-sync.
In those cases, uncheck the Resync Data checkbox right before pushing to production and the new SQL logic will be used moving forward, without modifying the historical data. 🎉
Useful when:
- Migrating transformations to use new schema
- Accommodating logic that applies to new data only (ie. changes to the utm structure)
- Historical processing takes a long time and implementing the new logic historically is not a priority
Note, any transformation can still be resynced at any point, so it's recommended to use separate transformations for any historical logic that needs to be maintained (ie. migrating to a new data source). This way, the transformations can be maintained and managed independently.