You’re offline. This is a read only version of the page.
4
Hi,
I'm new to Pwoer Platform CLI.
I'm having issue when trying to export a portal from 1 environment to another environment.
This is the documentation that I follow: Migrate portal configuration - Power Apps | Microsoft Docs
The error that I got is "Error: Portal entities are not available on this org, please install portal package on the org."
Not sure what and where the issue is.
Thanks
Hi @aldvintumbelaka ,
sorry for the late answer. We had several tries with the CLI and it worked in all scenarios.
The only thing i can imagine is, that you are trying to transport a servcie portal to a non service dataverse. That might fail.
All other situations are handled by the tool quite well. Even creating from scratch works great. Fro my machine and from devops as well.
Sorry to be no help in this,
Christian
After trying few different cases and try to create a fresh start portal to test the migration, I magae to migrate the new portal to other environment.
But, I still have issue with my original portal.
What other possibility is because of the portal that I can't move is actually has quite lots of test data that might break something.
And I can't use the migration tools because the procedure to get a software installed is quite complicated.
I am not sure about the CLI, but you also get that type of error when the type of Portal is different between the source and destination (e.g. Source = Customer Self Service, Destination = Blank/Custom), (if the same type also check that the Source version is the same as the destination have also seen this stop the move but with slightly different error message)
From the same official link, use the configuration migration tool. Instead of CLI
Please try and let us know the outcome.
Hope it helps.
------------
If you like this post, give it a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.
Hi @aldvintumbelaka ,
hm, sounds strange. To be honest, we usually do not delete the portaldata prior to transport as it updates the data if its the same portal or creates it, if its a diffrent portal.
Unfortunately the guy doing this in our organization is available from monday on. I will ask him about that process (we started using devops for that, which is itself using the cli tool)
May be a dumb question: you are connected to the right dataverse for the target? And all tables were generated (this may depend on the template used to create the source: when you used sth. service related you may have more table s for the portal as if you only used a custom portal (at least, i think, but not sure 🙂 )
So, will ask my colleague on monday about issues of that type.
Have fun,
Christian
Yes, I've created the portal and delete the autogenerated website and portal, but not the portal management as per the documentation number 1-3.
I've also export the table from the source and import it to the target as well.
Hi @aldvintumbelaka ,
not sure, whether this is already the cause, but you have to install portals first in your target environment. This does basically two things: it creates portal entitiestables in your dataverse and it creates a webserver serving this specific portal.
The clienttool does not create tables to my knowledge, it transports data.
Yo do not have to create the same portaltemplate in your taget (even if i would recommend to do so), the site which is served can be changed either in the used websitebinding or in the backendadministration.
Hope this helps,
Christian
#1
Lucas001
60
Super User 2025 Season 1
#2
Fubar
55
Super User 2025 Season 1
#3
surya narayanan
35
Share
Report
All responses (
Answers (
