Share
ReportHi,
Hopefully this is a problem someone else has come across before and may have a few tips and tricks to reduce the pain/risk.
I've inherited a project that requires two sets of Dataverse data to be merged into one environment but it's messy and some history may help with the understanding.
About a year a go a copy of an existing Model Driven app was imported to a different PowerApps tenancy. Since then both apps and Dataverse have been developed further resulting in additional lookup and choice values.
Where the new values are unique, namely no corresponding/matching entry in the other system I expect these to be straightforward to migrate/merge.
However, the problem arises where we have matching choice and lookup names but different IDs/GUIDs and in some cases matching IDs/GUIDs but different names.
In the old SQL world, if there wasn't too much data, you could simply export to csv, find and replace, import and merge the data to it's new home.
I'm hoping that there is something much easier with Dataverse... note we are talking about pulling the data out of once tenancy and moving/merging this to another tenancy.
To add a level of complexity, there is a mixture of matching records and new records that link back to the choices and lookups.
The first stage is to merge the data into a single Dataverse instance and then bring over the Model Driven app from the old environment to use the (now) shared Dataverse instance. This will mean two Model Driven apps running off the same Dataverse instance. There is then a task to review and amend as required business rules and flows, etc. which should be straight forward once all the data is aligned up correctly.
All suggestions welcome.
Categories:
All responses (
Answers (
1,526
