I love this feature, as it can also be used to quickly incorporate datawarehouses made when TimeXtender was not used yet.
I gather that it was created because the Export/ Import feature from version 20.10 is no longer (or not yet?) available.
However, when taking a database, created with TimeXtender, it unfortunately simply also takes in the raw tables, Log and Message tables (as the gif in your article clearly shows). This means actually that you need to clean up a lot of “ingested” tables from the solution and remove all the system fields, like DWID, because the deploy just doesn’t work otherwise.
If it wouldn’t take too much work, it would be great to have an option to
- Choose a Schema to import. If best practices are followed, then only the Valid schema should be enough.. and it would allow to import a Staging area only, or a Final area only
- have a check box to remove any fields which would conflict .. and thus not scripting any of the system fields which TimeXtender will add again.
Until this is made, I’ll work on with a custom solution because I believe this feature offers the opportunity to refrain from re-inventing the wheel over and over again, but to inject template sets of tables and views to gain even more time.
