Deploy Power Portal with multiple portals on source environment

(0) Share

Report

Posted on by l.oliver

147

Hi,

I have a source environment containing two portals (Blank portal template) with different user requirements.

Lets call them "portal A" and "portal B".

Now I have a target environment where I have first, imported the same CRM solution from source evn. Then after import completed I provisioned a portal from blank (to get the portal management application installed).

Now I have a "portal C" in the target environment.

Next, I install the "DataMigrationTool" and download the "Blank Portal"-template from the Microsoft documentation page.

I export using the schema file and import into the target env afterwards.

Now I see the 3 website records (A, B, C) in the target env.

The (target env) original "portal C" seems to have now include both configurations from "portal A" and "portal B". So basically, "portal C" is totally messed up with routing to different pages, templates, etc.. A really pain in the #¤%.. 🙂

I tried to create a new "portal D" in target env and use the "Use data from existing website record". But this seems to not work either, as the pages, templates, etc. all have directed randomly to portal "A", "B", and "C".

Is this all because the target env is located in another tenant?

Categories:

Power Apps portals

I have the same question (0)

All responses (3)

Answers (1)

Community Power Pla... on at

Like (0)

Report

Hi @oml , when you use "Custom Portal - Blank Portal" scheme in the portal migration tool
https://docs.microsoft.com/en-us/powerapps/maker/portals/admin/migrate-portal-configuration
you are basically asking to move all files linked to "blank portal" which based on what you explained you have 3 so it will move 3 UNLESS you modify the fetch xml file to add new filter by "website id" for example so in this way you will pick a "blank portal with ID = C" and you will move only C

Another option you can use XRML tool box to migrate specific portal regardless of template
https://crmsuccesshub.wordpress.com/2018/04/24/xrmtoolbox-tools-for-microsoft-dynamics-365-portals/

Hope this help

Was this reply helpful? Yes No
l.oliver 147 on at

Like (0)

Report

Hi @Anonymous ,

Thanks for the quick response!

I have been trying the Portal Records Mover with XrmToolbox (I have also tried to use the Portal Configuration Deployer in XrmToolbox).

So I still seem to have some troubles.. It looks like I can migrate only the one portal from source env now, which is nice. But, after the migration the portal in the target environment breaks. Like, I can't browser it and I get the "We're sorry, but something went wrong. Pleas....." - error.
I'm not 100% sure what settings I need to select in the Portal Records Mover.

I feel like I have tried every possible setting scenario, and still having troubles loading the portal in target env. Either I get the error above, or I get all the config records but they are simply not selected to the website... They are just there. Then I would need to manually select the right pages, templates. etc... And I don't believe that's the intention with the Portal Records Mover tool.

One thing I have noticed though is that the standard CSS (design) on the newly created Portal from Blank on target env is different from the Portal from Blank created some time ago on the source environment. Is this a problem or are the CSS files also migrated without issues with the Portal Records Mover?

Really appreciate your assistance!

**Also, should I delete any records in the target env created portal before moving the records? Like any of the standard records that are always created when you provisioning a portal?

Was this reply helpful? Yes No
Verified answer

l.oliver 147 on at

Like (0)

Report

So I opened a support ticket with MS and was told that the issues I was having could be caused by the limitations of the DataMigrationUtillity tools as of 1st October 2021.

The support agent from MS recommended me to download the Power Platform CLI to perform the Portal migration. Here is a link to the documentation.

This tool worked like a charm. No mixed-up records and no errors. The tool migrated everything without errors and the only thing I needed to do after the migration, was to update the portal binding to the new imported website record.

I will just mark this post as the solution to the issue.

Thanks again for the assistance, @Anonymous!

Was this reply helpful? Yes No