+2Good morning
We used the migration tool to upgrade from 20.10 to the saas version.
In the comparison of records in the MDW we miss out on the custom data which we use to insert -1 and -2 records.
Old situation:
After migration:
This is very inconvenient as this requires adding all custom data once more.
Best answer by Christian Hauggaard
+5Hi
It would seem like the custom data isn’t migrated.
If you manually add it again, does it get removed, or does it stay?
+2Hi Thomas,
I am adding them all manually again as that is the fastest solution for now (then it stays in the project).
Reason for this ticket is to let you know so maybe the migration tool can be updated to take along the custom data for future migrations at other customers.
Greetings, Roy
+5Hi
That is fair, I was just checking to see if there was more to it than that. Whether it is a deliberate limitation or a bug I don’t know, I will have to check internally.
+2Thanks. Have a nice day.
+2Hi Thomas, no we did not, we created a copy of the azure database instead.
+5Hi
It can be an issue with the schemas. Do you have a default schema on the data warehouse in LTS? When we convert a data warehouse from LTS to SaaS, we set up a default schema if one is not there, or if there is one with the same name, we rename it. If this is the case, they need to change the schema in the new database.
+2No we have are own schemas in that layer. For me the ticket can be closed as we entered the data manually again. Hope this is no issue for other customers.
+7Hi,
is this on the roadmap for fixing as this is used quite frequently?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
