+1We need a way to roll a solution back to a prior version of Data Ingest and Data Integration. I’ve spoken to several partners, and there is a bit of “TDI upgrade anxiety” at the moment.
In the olden (v20) days, I just backed the project repository up but we can’t do that in the modern cloud world … roll-back was in those days a simple matter of removing the upgraded project repository and restoring the backup.
If anyone has a solution that overcomes “upgrade anxiety”, then please share 👍
+8Hi,
the current process would be something like:
It would be nice if you could mark an instance so that that state is “kept” and you could revert back to it from the portal without needing to clone everything. How rigorous or not you decide to test upgrades also depends on the impact of the upgrade, if there are no deployable changes it is likely easier to evaluate than if the implementation of history or incremental tables is involved.
+1Hey mate,
The problem is, as far as I can see, that you lose all table and field selections in the data source.
And if you got 100s of tables with 1000s of fields…
But I follow your line of thinking 💪
Maybe we just need an option to clone a data source with table/field selections (and all other metadata such as query tables, datatype overrides, primary keys and incremental rules) preserved.
In fact, maybe cloning should preserve selections and metadata automatically as it’s easy to clear everything or select everything, as required.
+8Hi,
the new release allows you to export/import metadata settings so that should at least make it possible 😁. I fully support cloning in the portal giving you the option of taking across the metadata settings in one go!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
