You’re offline. This is a read only version of the page.
12
Do we have Publishing option in Power pages? like once the content owner done with all the changes on a power page, can they publish/submit it for manager approval? Is there any way we can send a flow for the approval. Once manager approves the page should be available for external users to view. Is this possible in Power pages?
Hi @ragavanrajan ,
I'm really interesting to know more détails in method 2 because maybe we're chosing this option:
* By default power pages will expire after 30 days even if this is an production environment, do we have to convert all our power pages in dev, test from trial to production, otherwise we have to create again power pages to continue evolving ? what will be your recomendation, if this is the only option could be this expensive ?
* And about urls, do we have to define a custom url for each environment exemple : dev-name-site-web, test-name-site-web and for production we remove prefix and it will be site-web ?
Thanks so much !
Hi @HarshaKudum
There is no flow template yet. You can use dataverse trigger and use the table which I have mentioned and utilise the publishing state column to achieve your need.
Combining Approval automate flow is possible but thinking loud requires a bit of effort.
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.
This Publishing state could help us. Thankyou @ragavanrajan we are glad from the responses. One final question, Do you think we still require a flow to automate this process? I wonder if Power automate has a flow template to automate this publishing process. When Content owners are done with their changes, they should have a button on each page to submit for approval and it should trigger an email for managerial approval. Once it is approved/published = yes, it is ready for public or anonymous users to view the page changes. Is this feasible in Power Pages?
Thanks much!
Also forgot to mention. You can implement the publishing state as well. Different portal templates is currently supporting this.
For some reason, I couldn't see the table. Would you please send the related article how we can set up automate flow on page edit approvals in Office 365/Power Platform.
I would accept this as solution for my query.
I did. Adding again for your reference.
"Web Page (adx_Webpage)" Table.
Good luck @HarshaKudum
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.
Have you forgot to add the table for power automate flow? I don't see any table in the response
Hey @HarshaKudum
That's cool. Thanks for sharing your current scenario.
As mentioned, using method 1: you can innovate via power automate using approval flow. Please check the below table I have mentioned for your power automate flow.
Using method 2: FYI: One Tenant is referred here. I am referring to creating "multiple environments" using the power platform admin centre. You have few options here to move content between environments
1. Use the official configuration migration utility
Note: Choose GUI or PowerShell.
2. Use XRM Toolbox- portal record movers
https://www.xrmtoolbox.com/plugins/MscrmTools.PortalRecordsMover/
3. Setup a CI/CD pipeline using Azure Devops
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.
Thanks @ragavanrajan ,
We are using SharePoint 2013 On Prem server to host our external website. We currently have multiple content owners who are editing our external faced web pages. Each of them checkout & make changes and check-in back all their changes. Once all of the content owners complete the page edits, there is a special team of members who takes the final call in publishing & approving the final version of each page. We don't want to display these page edits to external users until it is approved by the special team. In Method 1: is there any way we have approval rights? that only special team can approve the page edits? In Method 2: How can we have multiple tenants in Power Platform, I believe is this something like by creating different environments in Power Platform? If this is the case, How can we move changes approved in Dev environment to Prod environment?
Thanks for providing some insights
Harsha
Hi @HarshaKudum
Some insights to achieve your expectations differently.
Method 1:
1. Unlike other CMS, Power Pages works quite different. Power Pages is a WYSIWYG editor with advanced security mechanisms applied for data.
2. You can create custom web roles for your use case with edit privileges rather than admin roles, create a relevant web page access control rule for a specific page you wish to allow, and set the rights to "Grant Change".
You can innovate through Power Automate and choose the "Web Page (adx_Webpage)" table for your approval to automate flow.
Method 2:
Using ALM to achieve your needs. The best practice is to spin up environments ( Dev, Test and Prod) and allow your users to work on the application lifecycle.
For instance Dev > Test > [Pre Prod] > Prod
1. Review the changes in one environment, then move the stages to a different environment once you are happy with the content.
2. Set up a CI/ CD pipeline if required
Advanced: Signing up for a developer plan is also an additional choice for you. So they can work on their own environment.
https://powerapps.microsoft.com/en-nz/developerplan/
Hope it sheds some lights
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.
#1
Fubar
69
Super User 2025 Season 1
#2
oliver.rodrigues
49
Most Valuable Professional
#3
Jon Unzueta
43
Share
Report
All responses (
Answers (
