Flow (using HTTP request) to create SharePoint site page by copying SP outputs produces 'Bad Gateway'

[J_Taylor]

I found a very helpful video about creating a SharePoint site page using some of the source network outputs (of creating a page manually from SharePoint) - see screenshot below for the rough idea. I noticed the request headers and thought that it might be easier to use all of the content from the API request in one step rather than doing several steps. However, when I try to run the flow, I always get a 'badgateway' error.

The flow is just one HTTP request (peek code below with body removed) :

{
    "inputs": {
        "host": {
            "connectionName": "shared_sharepointonline",
            "operationId": "HttpRequest",
            "apiId": "/providers/Microsoft.PowerApps/apis/shared_sharepointonline"
        },
        "parameters": {
            "dataset": "https://XXXXXXXX.sharepoint.com/sites/InclusiveEducationTemplate",
            "parameters/method": "POST",
            "parameters/uri": "_api/sitepages/pages(24)/SavePage",
            "parameters/headers": {
                "accept": "application/json;odata=verbose",
                "content-length": "4963",
                "content-type": "application/json;odata=verbose"
            },
            "parameters/body": ...
        },
        "authentication": {
            "type": "Raw",
            "value": "@json(decodeBase64(triggerOutputs().headers['X-MS-APIM-Tokens']))['$ConnectionKey']"
        }
    },
    "metadata": {
        "operationMetadataId": "92d5bc62-0bd8-41e7-9791-28d9d48edfa8"
    }
}

Initially, the headers from the network source code were longer, however, they did not seem relevant. The exception to this is "content-length": "4963" which was required or would produce the error: "We cannot save your changes because a site member has ended your editing session. Refresh the page and click Edit to continue making changes." This error also occurred when the body did not include extra escapes (\" produced the error, but \\\" did not).

I have read other posts about "badgateway" occurring when dynamic content is used. However, I am not using any dynamic content yet.

Also note, the new site page is effectively copying the page and data (links to document and list - 123456_DOE, John.docx and 123456_DOE, John, respectively). The name of the new site page is 234567_DOE, Jane.

If anyone can help me see my error?

@PrakashMaithani, @grantjenkins, @SudeepGhatakNZ, @Sundeep_Malik, @Rhiassuring, @Expiscornovus, @ScottShearer, @srduval ?  

Your assistance is greatly appreciated.

Headers-JSON.txt containing the complete headers from SP

Body-JSON.txt containing the complete body from SP

[grantjenkins]

Just wanted to clarify what you are ultimately trying to do here. Are you just trying to copy an existing Site Page to the same site / another site? Or was there more you were trying to do?

[J_Taylor]

@grantjenkins, I have a template site page and I want to copy that using a flow. That is, so that I don't need to manually create the site page through SharePoint. 

More specifically... The video does go through and explain somewhat how to do that. However, I wanted to take the steps further. For example, the video showed about how to use a piece of the Request Payload - I am using the concept, but applying a different request.

Does that make sense? If not, I can try to clarify further. 

[grantjenkins]

If you are just wanting to copy a page as a new name in the same site, then you can do the following:

/_api/web/getfilebyserverrelativeurl('/sites/PowerPlatformTesting/SitePages/Template-Page.aspx')/copyto('/sites/PowerPlatformTesting/SitePages/@{triggerBody()['text']}.aspx') 

If you were after something else, please let us know.

[J_Taylor]

I am trying to copy all the content of the page, and change the links on the page.

The video seems to prove that it is possible. I am trying to make small changes from what the video establishes.

[grantjenkins]

EDIT: Ignore what I originally wrote in this post around PowerShell, etc. Finally got it working.

I've was playing around with the stuff in the video for a while and getting the same errors as you. Then finally got it to work. Will write what I changed from the video and post my solution here later.

[grantjenkins]

@J_Taylor 

Things I changed that initially gave me errors.

I had put an incorrect URL in one of the HTTP requests - silly error but worth checking.

Get file metadata was asking you to add some encoding directly into the File Identifier. This was giving me grief so just encoded it properly using encordUriComponent which resolve the issue.

encodeUriComponent(concat('SitePages/', triggerOutputs()?['body/Title'], '.aspx'))

Someone in the chat mentioned making sure to have SitePages instead of sitepages in the Uri. Not entirely sure if this would cause an issue but changed all mine to SitePages.

Originally, I tried to bypass the check-out step but found I needed to do this prior to saving the page as a draft with the payload.

You can also check to ensure you haven't used the ID from the trigger, but rather from Get file metadata.

When I got it working, I was able to change the Name, Job Title and Employee Number as per the Video, and also the main Image on the site. I would assume a Quick links webpart would also be fine to modify in the payload. I also changed the Title of the Page at the bottom of the payload to the Title from the Trigger.

[J_Taylor]

@grantjenkins, Thank you for going through the process of making it work for yourself. I will try to add the other steps soon.

What do you think is the difference between creating the site page in multiple steps to creating it in one step? I tried to use the Network output to just create the page (the created page will have dynamic content in the future, but I haven't added that yet).

I changed the the Uri to SitePages, but I don't think that was the only issue as I am getting a time out issue badgateway issue (the test timed out, but the official error when I later checked was "badgateway").

[J_Taylor]

@grantjenkins, I have now created all the steps in the video. However, I am still getting a 'badgateway' error. I wonder if you can see my issue?

This all works successfully. The page is created and then checked out. I did see your comment about 'Get file metadata', but I figured if it wasn't broken...

The error message is: 

There was an error deserializing the object of type Microsoft.SharePoint.Publishing.SitePageFieldsData. Encountered unexpected character ' '.

All the body can be found here: Body-JSON.txt

[J_Taylor]

I found the error. My body was wrong. There were spaces where they shouldn't be (\ "). I was investigating changing the format with a JSON parser and it informed me there was an issue.

I also added a HTTP request to publish the page - which worked well.

I am still playing around with creating the page in one HTTP request. Initially, the content-length was too short. I tried 10,000 ("Bytes to be written to the stream exceed the Content-Length bytes size specified.") and also removing it ("We cannot save your changes because a site member has ended your editing session. Refresh the page and click Edit to continue making changes.") with no success. I also tried changing the api request to "SavePageAsDraft", but I still had the "...cannot save your changes..." error.

Do you have any thoughts, @grantjenkins? Would the header content-type be required for a successful result since the HTTP request lasts longer (tries two or three times over 10 minutes) than without the content-type in the header (which just fails immediately).