I have an Environment with 2 solutions, 1) A Canvas Admin App 2) A Website (PowerPages).
I would like to build a Solution and add the PowerPages (web pages) in the solution to deploy it to PROD environment.
Is it possible? If it is not, which is the workaround?
PS. I've seen an option to add "Pages" to a Solution but none of my pages were available when I tried it. Wondering if there is a way to make it.
Thanks,
Raf
Solved! Go to Solution.
This shouldn't be a problem, happens to me every now and then.
The steps in order are:
- Create the portal template in Dev (you already have)
- Use pac cli to upload the portal from PoC to Dev (you'll have 2 websites there for now)
- Go into the Portal Administration page and change the website binding from the template to the one you want. To do this go to:
make.powerapps.com -> Select environment on top right -> Apps -> Select the ellipses on the Portal App -> Settings -> Administration
On the new page that comes up, scroll to the bottom and change the Portal Binding from the template to your new uploaded website:
- Click update and wait a few minutes.
You should now be able to browse to your website.
And now is when you can delete your default template website, not before otherwise you screw up a lot of the config... we all learn that the hard way...
@rtardelli
Deploying of Portal is possible. You can use the Portal CLI to deploy to the target environment or good old Config Migration.
I follow this approach:
1. Add all my customizations specific to my portal into a single solution (forms, views, plugins etc that are specific to your portal).
2. Export this solution
3. Export related Portal configuration (either CLI or Config Migration)
4. Push this to the target in Pipeline or via CLI manually.
https://learn.microsoft.com/en-us/power-apps/maker/portals/admin/migrate-portal-configuration?tabs=C...
https://learn.microsoft.com/en-us/power-apps/maker/portals/admin/migrate-portal-configuration?tabs=C...
Hi ,
Thanks for helping.
I am trying to add the webpages in the solution I created. But none of my pages are available. Any idea why ?
I have an option to add the "Site Map" which I believe will bring other required objects to the Solution. Is it a good way to make it ?
Thank you.
Rafael
Hi @rtardelli
Unfortunately there's no way to add Power Pages to a Solution, they're not solution aware. To deploy Power Pages you should use one of the options @eugenevanstaden mentioned. The option you have there is to add a Custom Page to your solution which is not the same thing as Power Pages.
You need to first move any Dataverse Solution with Tables and fields used by the Portal/Power Pages. You'll also need to ensure you already have a website provisioned on the destination environment.
After that you should be able to use either the configuration migration tool or the Power Platform CLI to move your portal from one environment to another.
I personally use the CLI so I'll leave this link that hopefully will help you: https://learn.microsoft.com/en-us/power-apps/maker/portals/power-apps-cli-tutorial
Hi Joao,
I tried follow the tutorial to copy the environment, but it is giving an error. At the end nothing changed.
Started uploading website data
Connected to...xxxxxx-powerpages-dev
Loading Portal Manifest...
Manifest loaded successfully.
Upload completed for table: adx_adplacement
Upload completed for table: adx_polloption
Upload completed for table: adx_webpageaccesscontrolrule
Upload completed for table: adx_poll
Upload completed for table: adx_publishingstate
Upload completed for table: adx_entitylist
Upload completed for table: adx_websiteaccess
Upload completed for table: adx_entityform
Upload completed for table: adx_tag
Upload completed for table: adx_webrole
Upload completed for table: adx_entitypermission
Upload completed for table: adx_pollplacement
Upload completed for table: adx_website
Upload completed for table: adx_ad
Upload completed for table: adx_pagetemplate
Upload completed for table: adx_weblinkset
Upload completed for table: adx_sitemarker
Upload completed for table: adx_urlhistory
Upload completed for table: adx_portallanguage
Upload completed for table: adx_websitelanguage
Upload completed for table: adx_entityformmetadata
Upload completed for table: adx_weblink
Upload completed for table: annotation
Upload completed for table: adx_webfile
Upload completed for table: adx_sitesetting
Upload completed for table: adx_webtemplate
Upload completed for table: adx_contentsnippet
Upload completed for table: adx_webpage
Upload completed for table: adx_websitelanguage
Upload completed for table: adx_website
Upload completed for table: adx_webpageaccesscontrolrule
Upload completed for table: adx_adplacement
Upload completed for table: adx_polloption
Upload completed for table: adx_poll
Upload completed for table: adx_webrole
Upload completed for table: adx_tag
Upload completed for table: adx_portallanguage
Upload completed for table: adx_urlhistory
Upload completed for table: adx_entityformmetadata
Upload completed for table: adx_publishingstate
Upload completed for table: adx_entityform
Upload completed for table: adx_pollplacement
Upload completed for table: adx_entitylist
Upload completed for table: adx_websiteaccess
Upload completed for table: adx_entitypermission
Upload completed for table: adx_pagetemplate
Upload completed for table: adx_ad
Upload completed for table: adx_weblinkset
Upload completed for table: adx_sitemarker
Upload completed for table: adx_webtemplate
Upload completed for table: adx_weblink
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Updating table adx_webfile with record id:5480ce4c-bc29-ed11-9db1-00224814df64 FAILED due to Subject With Id = 672845db-5f1b-ed11-b83b-002248144a90 Does Not Exist
Upload completed for table: adx_webfile
Upload completed for table: adx_sitesetting
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:691164eb-8f40-6393-9ae1-64e0d2350f25 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:d7945043-511a-2f32-a291-872038c9b31f FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:f760cc0b-45b3-eaa2-84d3-cd100704d4c3 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Updating table annotation with record id:dd0e0f6b-c318-6c04-8a82-17fb7f7eaa04 FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Upload completed for table: annotation
Upload completed for table: adx_contentsnippet
Upload completed for table: adx_webpage
PS C:\Users\Ra\OneDrive - Rio Tinto\VStudioCoding> pac paportal list
Connected to...xxx-powerpages-dev
Completed listing portal websites
Actually my yml file didn't work. What happened is that my upload created all rows (entities) in the portal management with the downloaded name. Now I have everything duplicated in the Dev environment.
Hi @rtardelli
Let's see if we can sort these one by one.
First: Updating table adx_webfile with record id:GUID FAILED due to Subject With Id = GUID Does Not Exist
Do you have a lookup to a Subject entity from the webfile? I don't recognize that one but seems to be failing the upload because the subject records aren't on the destination environment. Never tried this but you might be able to use the include_entities parameters of the download command to include that entity if you really need it.
Second: Updating table annotation with record id:GUID FAILED due to The attachment is either not a valid type or is too large. It cannot be u
Should be a simple one, don't think this is a file size issue. It might be trying to upload javascript files, that's the classic example, and they are by default on the restricted attachment list. But just to be sure find the adx_webfile it refers to and confirm the file type.
Then follow this guide to get to the list of restricted files, you should see that file extension there, remove it, save it and try again.
Regarding the duplicate website records. I'm a bit surprised, the download and upload is based on the main website record GUID, uploading to the same environment should just update the same records... really not sure what happened there. But if you want to delete one of them that should be simple, go to the Websites view, select the duplicate and hit delete, that should cascade the delete down to all the website records.
But please do confirm first if you are actually deleting the duplicate records and not your website! Like I said, I'm a bit surprised it created a duplicate in dev.
Lastly, you might have guessed it already but you need to change Authentication profile before uploading the portal. Should be:
- pac auth create -u <dev environment url>
- pac download --path "C:..." -id <portal guid> -o true
- pac auth create -u <test/prod environment url>
- pac upload --upload "C:..."
Hope these suggestions help
Hi Joao,
I have a poc environment with all development done. This is only a POC environment we used to discover PowerPages.
Now we created the Dev environment by selecting a default template. This new Portal with default template already has a WebSite with a GUID which is totally different from the POC environment GUID.
The challenge is how to deploy from POC (all pages / developed JavaScripts) to DEV replacing and not duplicating the WebSite entity and all other rows in Portal Management.
I also tried to drop the "template" Website in Portal Management in Dev, which made a cascade delete, but there are still other parameters, and it didn't work well.
I ended up recreating again the Dev env because it was a mess.
Now I only have the template there. If I try again following the tutorial it will duplicate the rows again in Portal Management.
Should I reset the Dev environment meaning that it will delete the template portal rows on Portal Management?
https://learn.microsoft.com/en-us/power-apps/maker/portals/admin/reset-portal
Then I will have an empty environment and I can run the upload command (CLI)?
Thanks for helping. Looking forward to hearing from you.
This is the template page I selected.
The language is US for both environments (POC and DEV).
This shouldn't be a problem, happens to me every now and then.
The steps in order are:
- Create the portal template in Dev (you already have)
- Use pac cli to upload the portal from PoC to Dev (you'll have 2 websites there for now)
- Go into the Portal Administration page and change the website binding from the template to the one you want. To do this go to:
make.powerapps.com -> Select environment on top right -> Apps -> Select the ellipses on the Portal App -> Settings -> Administration
On the new page that comes up, scroll to the bottom and change the Portal Binding from the template to your new uploaded website:
- Click update and wait a few minutes.
You should now be able to browse to your website.
And now is when you can delete your default template website, not before otherwise you screw up a lot of the config... we all learn that the hard way...
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 1: Community MembersSolutionsSuper UsersSolutionsPower Pages @Inogic 1 @ragavanrajan 2 @aofosu 1 @Jcook 1Open @OliverRodrigues 1Open @Lucas001 1Open Open Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Pages @taraubianca25 2 @EmadBeshai 2 @ALP2 2@Fubar 2 @ekluth1 2@ragavanrajan 1 @mandela 1@OliverRodrigues 1 @Ajlan 1Open @elishafxx 1 @TA_Jeremy 1 @helio1981 1 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower PagesInogic2@EmadBeshai 6Ajlan1@ragavanrajan 4CraigWarnholtz1@Fubar 4 @Jcook 3 @OliverRodrigues2 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower PagesHenryed071Fubar3Inogic1OliverRodrigues2JacoMathew1EmadBeshai2faruk11 TA_Jeremy1 shubhambhangale1 doug-ppc1 hubjes1
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages