Overview
If you replicate tables from your own database into Daasity (for example NetSuite, Postgres, SQL Server, Snowflake or BigQuery), you can now adjust what's being pulled without rebuilding the setup, and you'll be warned before a change would break it.
What we changed
You can now edit an existing table replication to add a filter or bring in another column, instead of deleting it and starting over. If an edit would cause data to load incorrectly, it's stopped before it's saved with an explanation of what to change. You can also see progress while a history load is running, and you'll get a heads-up when a setup would re-read the entire table on every refresh, which slows down how quickly your data is ready.
We also fixed an issue where columns you renamed during setup were arriving empty in your reporting.
What to expect
No action is required for most merchants. If you renamed any columns in a table replication, run a history load on it so earlier data fills in. Database Replicators walks through the full setup.