Answered

PowerApps Portal: Migrate portal configuration using Configuration Migration Tool

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

Hello Community,

I have a custom PowerApps portal created and linked to a Dynamics 365 dev environment. I follow the Microsoft article below to use the Configuration Migration Tool to export the portal configuration from the source (D365 dev environment) for importing into the target (D365 production environment).

https://docs.microsoft.com/en-us/powerapps/maker/portals/admin/migrate-portal-configuration

I followed all the instructions from the article above, including using the custom portal schema file. After the export is completed, I notice on the export screen of the Configuration Migration Tool it says 30 entities have been exported.

I am curious as to why it would export that many entities in this case, because I am definitely not using 30 entities for the portal. I assume it's including other entities in the D365 dev environment? I just want to be sure when I import this export file into the target D365 production environment it won't cause unnecessary problems or accidentally overwrite other unintended entities? My expectation is that the export file should only contain the components related to the custom portal.

Any insights would be appreciated!

Thank you!

Categories:

Power Apps portals

I have the same question (0)

All responses (6)

Answers (1)

Sort by

Christian Leverenz 1,214 on at

Like
a
(2)

Report
Copy link

Link copied!

Hi @Anonymous ,
as always, it depends 🙂 without really looking into portals, you have at least websites, webpages, content snippets, (site settings), page templates, web tempaltes, notes, attachments, webroles, entity permissions, entity forms, entity form metadata, webforms, entitylitsts, access control rules, website languages, (portal languages), web links, web link sets, site markers, the m-n relations between entity permissions and webroles (other m-n relations??)
these already make up more than half of the 30. If i look in the dynamics navigations, there are some more things (well, contacts should not be transported 🙂 ) so this number sounds reasonable.
I never used the configuration/migration tool but when it respects the ids (guids) of the entries there should be no problem of overwriting stuff.
Nevertheless:
When we transport portalstuff there are things, we only transport initially. Especially site settings are in my opinion "site settings" which usually differ between systems. Some snippets may also be not great to transport, for example navbar left may be "test system" in one case and "mycompany" in the other system (but i think you have no choice to transport only specific entries)
Hope it helps and points in the right direction,
Christian

Was this reply helpful? Yes No
oliver.rodrigues 9,482 Most Valuable Professional on at

Like
a
(3)

Report
Copy link

Link copied!

I would recommend using the Portal Records Mover from XrmToolbox

------------
If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @chleverenz ,

Thanks for the details, much appreciated as always! 🙂

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @OliverRodrigues ,

Thank you for the recommendation! I will look into this option accordingly.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @OliverRodrigues ,

In your experience when using the Portal Record Movers from XrmToolBox to migrate one PowerApps Portal solution/configurations from one Dynamics 365 environment (source) to another Dynamics 365 environment (destination), would you know if the following sequence matters?

1. Provision portal app in the destination (portal URL in the destination will be different from the portal URL in the source)
2. Import related Dynamics 365 solution from source environment to destination environment
3. Export portal solution/configurations using Portal Record Movers from source environment and import to destination environment

Do I have the right sequence above, or the order of sequence doesn't matter?

Any insights would be appreciated.

Thank you!

Was this reply helpful? Yes No
Verified answer

oliver.rodrigues 9,482 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

I normally go for the same sequence as you mentioned there

but between D365 solutions or Portal records, it doesn't really matter the sequence
this is because the Portals stores everything as text and not lookups/entity reference

Was this reply helpful? Yes No