If you update a boolean field and add a condition to check that field to prevent looping when the flow is re-triggered by the update, news post pages are always left in an "unpublished" state because the last action updates a field. I tried changing the promoted state field to "2" which technically means "published", but the pages still have to be manually republished. And of course, when you do that, you trigger the flow to run again!
The lack of a "publish" action is more of an annoyance than a critical issue, but is there any way to incorporate page publishing in a flow?
Solved! Go to Solution.
See: This seems to be achievable using SharePoint API and is explained in the following blog: News Scheduling in SharePoint using Power Automate aka Flow Part 3: https://purple.telstra.com/blog/news-scheduling-in-sharepoint-using-power-automate-aka-flow-part-3
Ellis
See: This seems to be achievable using SharePoint API and is explained in the following blog: News Scheduling in SharePoint using Power Automate aka Flow Part 3: https://purple.telstra.com/blog/news-scheduling-in-sharepoint-using-power-automate-aka-flow-part-3
Ellis
Thanks @ekarim2020 - all that was needed in my case was the send http request action, which republishes a page and oddly doesn't trigger another Flow run even though the file has changed!
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
Come together to explore latest innovations in code and application development—and gain insights from experts from around the world.
At the monthly call, connect with other leaders and find out how community makes your experience even better.
User | Count |
---|---|
25 | |
24 | |
23 | |
23 | |
19 |
User | Count |
---|---|
58 | |
39 | |
38 | |
29 | |
26 |