Power Automate Copy SharePoint Page Content to another page in another site

This step is part for the large post

Duplicate Sharepoint Online Subsite with all Site Contents and Page[s] - Power Automate

But can be used individually.


The process is simple, in modern pages they did it so when you save/publish your page they send an ajax request with all the content, so you can just copy all that content and make your own HTTP with that content to update the desired page.


After this  you can browse this additional content

1 - copy page and add it to navigation

2 - edit the content that you copy



This is a 3 part tutorial

1 - get the data for page content

2 - prepare some data on item created (trigger)

3  - checkout / save  / publish page



Part 1 - get the data for page content

1. Open browser and go to your template page (page you want to copy)

2. Edit page 

3. Open develpopers tools (F12) and go to Network tab

4. Check the "Preserve log button"


5. Save/Publish the page

6. In the filter write "save"

7. Click View Source to change the date from parsed view to raw view

8. Ohh yes, copy it all!  Save it somewhere like in a list Multitext column or Notepad++




Part 2 - prepare some data 

In my case, following the main post, I created a new subsite and saved it in a helper list, which then triggers the flow and contains the target site url in its Title. Therefor the page rel url is fixed ("Home.aspx)

We need to know [purpose - step in following flow]:

a. When we want to copy (trigger the flow) -> When item is created

b. Source content (above step)                     -> saved somewhere

c. Target site url and page                            -> init var SiteFullUrl HomePageUrl

d. Target page ID                                          -> get file metadata



* EDIT: we had some problems with step "Get file metadata" one time duplicating the process and the solution was to wrap the "SiteFullIUrl" and the "/SitePages/Home.aspx" with encodeURIComponent()

On a side note to copy an existing page from site to site is most simple, and you can further automate that, and make it a Pre-Step for content copy instead my subsite creation

* IMPORTANT:

The values here, "/play-michal" or "/CollabHome.aspx" are just the specific files and sites we used in our dev enviorment. please change to your values as following:

"Current Site Address" - your source site from where you want to copy the page

"File to Copy" - the page itself in the source site

"Destination Site Address" & "Destination Folder" - as stated




Part 3 -  checkout / save  / publish page

These 3 action steps are identical except the last Uri fragment, and the body for the middle step


These are "Send an HTTP request to SharePoint" action step, and lets detail it:


a. The full site url

b. POST

c.  The 3 Uri are [ its always /pages(<itemId>)/ ]. I took the ID from the metadata step above.

    _api/sitepages/pages(@{outputs('Get_file_metadata')?['body/ItemId']})/CheckOutPage

    _api/sitepages/pages(@{outputs('Get_file_metadata')?['body/ItemId']})/savepageasdraft

    _api/sitepages/pages(@{outputs('Get_file_metadata')?['body/ItemId']})/Publish


d. Headers

    Accept              application/json;odata=verbose

    Content-Type        application/json;odata=verbose


e. No body but the save part (details and image just ahead)



In the Save HTTP action step you need to put all the content you copied with your browser



The End


In my case I also needed to change some data and used 2 - edit the content that you copy.





Comments

Post a Comment

Popular posts from this blog

OverTheWire[.com] Natas Walkthrough - JUST HINT, NO SPOILERS

game portal: http://overthewire.org/wargames/natas/ PASSWORDS for each level are stored in /etc/natas_webpass/natasX I made this walkthrough for people like me, i needed some help, but didnt want the spoiler, so here i will give you all the information needed to pass each level, yet not the solution. For levels needed custom web request i made a different post for powershell and javascript  with how-to's, since is a piece of learning for itself, and also for those of us that play at work and have only powershell at their hands. Although its not a complete spoiler there, its quite most of the solution so try yourself 1st. Natas The Natas game is from basic to advances web hacking. Every few levels is about whole new exploitation (with some harder ones doing comeback later), so a lot of learning. If you're new, you're the reason i am writing so much even for the 1st level, just please google EVERY topic you see, since in the following levels i assume you know the
Read more

SOLVED The item could not be indexed successfully because the item failed in the indexing subsystem

if you got an error like this The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Failed to recover content group; Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 04081656-B51B-4DCD-96D4-6DB2D2CEEEE7 ) as well as these: The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Caught exception when preparing generation GID[7]: (Previous generation (last=GID[6], curr=GID[7]) is still active. Cannot open GID[7]); Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 92EB0180-C086-4853-BED8-F4878D9748AD ) the solution for me was to clear configuration cache (PS)  and then restart SP Search Services. THX to m
Read more

Asp.Net Ending Response options, Response.End() vs CompleteRequest()

this blog is for any1 who get the ThreadAbortException when caling Response.End(), and then tried the other options such as HttpContext.Current.ApplicationInstance.CompleteRequest() and found out that there was no replacement. i'll start with the bottom line: if you want to stop right now your response and send it as is you dont have any other option other than Response.End(), period and it's the right thing to throw that EX in that case. the answer is its because there is the "HTTP pipeline" and the "Asp.Net pipeline", and CompleteRequest() cuts the HTTP pipeline but not the Asp.Net one so everything that is from handlers forwars (including all page events) continues but your part, the asp one, stays in your hands so that no information will be lost, so ur suppose to manage your code currectly, since information lost is really a bad thing, although in most cases we use Response.End() we know what we are losing and we want it. see this short article ab
Read more