I have power apps portal application on the trial environment, I wanted to migrate that portal on the production environment.
while migrating the configuration data using the configuration migration tool, it's throwing the below warning message and for some of the entities its not importing all the records,
I have a couple of other concerns below,
1. Does migration generates new GUID in the migration process, or it keeps as the previous one?
2. While migrating the web pages, I figured out some of the web pages are migrated into the localized content page, why it is I am not sure?
I really appreciate the quick comments on this.
Thanks for your post. I have a few answers below; Please take a look.
1. New GUID's are generated with each import of the data.
2. Looking at this issue, I am not certain why this was done either. I am guessing it has some issues during import with the hierarchy and failsafed to place them there.
Community Support Team _ Alex Rezac
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I just want to correct #1 there - @alrez is not correct, using this migration tool retains the GUIDS for the transferred records. This is important because it allows you to update the same records again from source to target in the future.
As for the errors, this is one reason I typically use Portal Records Mover - it will output a log file that's a little easier in identifying what issue occurred. As for Web Pages incorrectly being assigned as Localized Content, are you using the latest version of the tool? Does the tool indicate it disables plugins as part of its process? If so, did you create the list of entities yourself or did you use Microsoft's provided schema templates? These are important, as the latest tool and the correct file will disable the many plugins attached to Web Page creation (which will take even your Localized Content pages and attempt to make them Root Web Pages, and many other issues).
Link to Microsoft provided migration templates: https://docs.microsoft.com/en-us/powerapps/maker/portals/admin/migrate-portal-configuration
"Queued for second pass" means that it wasn't able to import it on the first pass and it will try it again later - usually this is because there is a lookup to a record that doesn't get imported until further down the list (or in CRM already). The key thing is if it imported on the second pass.
Same/different GIUDs - the answer is it depends. If you create your own schema you can get it to do either, if you used the ones by Microsoft for portal migration I think they are set to use the same GIUD's.
If you create your own schema by default it attempts to match on name (this is how you can get Parent and Local content mismatches as both records are in the same entity with the same names), in the schema setup/configuration you can tell it to match on id (GUID) rather than name.
Join us for an in-depth look at the new Power Apps features and capabilities at the free Microsoft Business Applications Launch Event.
Did you miss the call? Check out the Power Apps Community Call here.
We are excited to announce the Power Apps Super Users!
Check out our new profile badges recognizing authored solutions!