+1When you synchronize a data source and there are some problems, or the metadata changes are not to your liking (NoSql sources can be problematic), it would be good to have a choice to accept the metadata changes when you get the synchronization results before they are applied to the project.
In some situations, all the tables are removed because of a data source issue and you have to close the project without saving and open it again.
Agree!
Also, just because a column / entire table disappeared in the source, doesn't mean it should be removed from TX. This is especially true for historical tables.
I would also add the following options:
1. "convert removed tables to custom tables?"
2. "convert removed fields to custom fields?"
That way you can accept changes but your ETL won't break. You can fill the new "custom table" with data via a script for a quick fix.
We had this happen where the programmers at a customer decided to change all - to _ in the field and table names one day and we had to do direct SQL updates in the projectRepository to get it working again...
My post https://support.timextender.com/hc/en-us/community/posts/360042746452-When-synchronizing-a-source-add-the-option-to-Add-new-or-Retain-deleted-fields has a related suggestion, also with a way to quickly add new fields.
+5Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
