Uploading a file to SharePoint with GraphAPI

[chris421]

Hi all

I’m after some assistance with uploading files via GraphAPI, and hoping someone can help, as I can’t get past the “The Content-Range header is missing or malformed.” error….

So, the context…

I made a MSForm for one of the other departments to get requests – nothing fancy, just some questions and a file upload option. As I made the Form, the uploaded files get saved to my OneDrive. I’m now trying to create a Flow that completes various actions (after a Form is received); one of these, is to save the uploaded file(s) into the SharePoint library behind a Team that they use.

However, I won’t be a member of the Team after this is setup (so I can't use the standard save to sharepoint connectors), and I can’t guarantee who will be going forward (so don’t want to export and import on another account), so I’m trying to use Graph.

Also, the file may be quite sizeable, so I’m trying to cover all the bases and uploading as chunks.

I’ve been referring to the information here;

driveItem: createUploadSession

But the example is very vague….it doesn’t properly tell me how to actually upload the file.

My Flow seems to get the driveItem and create the upload session successfully, and I’ve got it picking out the Start and End bytes for the Content-Range….but it constantly tells me is missing or malformed….

 

 

 

Content-Range @concat('bytes ',variables('StartBytes'),'-',sub(variables('EndBytes'),1),'/',variables('FileSize'))
Content-Length (sub(variables('EndBytes'),variables('StartBytes')))

Hoping someone can maybe tell me where I've gone wrong.

Thanks, Chris

[Expiscornovus]

Hi @chris421,

As far as I am aware Content-Range is still one of the omitted HTTP headers in the HTTP action.

So, it would simply be removed from your request. And that might explain why you are getting a message that it is missing.

https://docs.microsoft.com/en-us/azure/connectors/connectors-native-http#omitted-http-headers

[chris421]

@Expiscornovus 

Thanks for the suggestion. Without Content-Range though, how would that action know which byte range to transmit?

However, still the same error without the Content-Range in the Header

I can't find a single, fully formed example using Power Automate and Graph to refer to anywhere....spent days Googling it.

Chris

[Expiscornovus]

Hi @chris421,

To be clear. I was not suggesting to remove the Content-Range header. I was just simply explaining why it did not work with this specific HTTP action because of a known issue.

Have you tried to use a different action for your Graph API request? Maybe it works with one of the Send an HTTP request actions or the Invoke an HTTP request action. That is worth a shot.

[chris421]

@Expiscornovus 

My mistake (I’ve added it back in now 😀)…would be nice if they were to sort the “known issues” so that things worked as they should!

Invoke an HTTP request still fails….although it’s not exactly forthcoming with “why” - just that it's a badrequest

Tried a Send an HTTP request (Group) connector

{
  "error": {
    "code": 400,
    "message": "URI path is not a valid Graph endpoint, path is neither absolute nor relative or resource/object is not supported for this connector. Resources: me,users,groups,sites,search,planner,teams,chats. Uri: https://TENANT.sharepoint.com/sites/BusinessIntelligenceTeam/_api/v2.0/drive/items/01MK5OREVNGZ7JWEPIQVHLJZDP7YZFJJFG/uploadSession?guid='3dc7111b-364a-44ce-9d5c-52c81d15ad17'&overwrite=True&rename=False&dc=0&tempauth=eyJ0eXAiOiJKV1QiLCJhbGciOiJub25lIn0.eyJhdWQiOiIwMDAwMDAwMy0wMDAwLTBmZjEgE2UwMC0wMDAwMDAwMDAwMDAvc2NvdHJhaWwuc2hhcmVwb2ludC5jb21ANmFlNjE0MWUtMTMyMy00ZTdlLThhMTEtY2RkOThjNjJkOgDhhIiwiaXNzIjoiMDAwMDAwMDMtMDAwMC0wZmYxLWNlMDAtMDAwMDAwMDAwMDAwIiwibmJmIjoiMTY2MjAzNTQ0OSIsImV4cDDFIjE2NjIxMjE4NDkiLCJlbmRwb2ludHVybCI6Ii9iWlcvckFHSkFERXBKeENCbmJKZzlGalVjUWhTZUdHWHNPcEl2QjU1Nm89IiwiZW5kcG9pbnR1cmxMZW5ndGgiOiIyMTAiLCJpc2xvb3BiYWNrIjoiVHJ1ZSIsImNpZCI6IllXVmhOV1JrTVdZdE9UbG1aQzAwT0ROakxUZzFZamN0TXpSbE4yRmpNakZrTXpkaSIsInZlciI6Imhhc2hlZHByb29mdG9rZW4iLCJzaXRlaWQiOiJZelZqTnpCaE4ySXRZamN3TWkwME5HUXlMVGhqTWpNdFltSm1aR0ZoTVRCaE9UazMiLCJhcHBfZGlzcGxheW5hbWUiOiJQb3dlckF1dG9tYXRlIiwibmFtZWlkIjoiYTgyNmJkZGEtZjBhYy00NWE0LWE3MTEtNjM2YWEyMDk0MjAwQDZhZTYxNDFlLTEzMjMtNGU3ZS04YTExLWNkZDk4YzYyZDg4YSIsInJvbGVzIjoiZ3JvdXAucmVhZCBhbGxmaWxlcy53cml0ZSBhbGxzaXRlcy53cml0ZSBhbGxwcm9maWxlcy53cml0ZSBhbGxwcm9maWxlcy5yZWFkIiwidHQiOiIxIiwidXNlUGVyc2lzdGVudENvb2tpZSI6bnVsbCwiaXBhZGRyIjoiNDAuMTI2LjMyLjEwMSJ9.NVhqNmZUUURFSGRZOWlHVGp5L0RCOWNZcFh2M0J0WTQ4Snh3WjZ0SGtXMD0",
    "source": "flow-apim-europe-001-northeurope-01.azure-apim.net",
    "path": "choose[9]\\when[1]",
    "policyId": "",
    "clientRequestId": "dd0f9d69-dd42-4213-ac0c-c93a92fe8b32"
  }
}

Tried a Send HTTP request to SharePoint (since destination is SP);

Guessing that it’ll fail when the “Do..Until” times out, as it’s already been running 20+mins for a 65Kb test file.

[Expiscornovus]

Hi @chris421,

Have you tried the same PUT request for the uploading of the file in Postman? Maybe that is a good way of checking if we are hitting another limitation/known issue or if it is a configuration issue.

[chris421]

That “Send HTTP to SharePoint” took just under 30mins to fail with 8 retries…

{
    "statusCode": 502,
    "headers": {
        "Pragma": "no-cache",
        "Cache-Control": "no-store, no-cache",
        "Set-Cookie": "ARRAffinity=d037289048130b578d80f263c75407cc35b0eab00e25d0eabb494426f92f413c;Path=/;HttpOnly;Secure;Domain=sharepointonline-we.azconn-we-003.p.azurewebsites.net,ARRAffinitySameSite=d037289048130b578d80f263c75407cc35b0eab00e25d0eabb494426f92f413c;Path=/;HttpOnly;SameSite=None;Secure;Domain=sharepointonline-we.azconn-we-003.p.azurewebsites.net",
        "x-ms-datasourceerror": "True",
        "x-ms-request-id": "14004b95-513c-49ad-a9bb-d890b8e532b0",
        "Strict-Transport-Security": "max-age=31536000; includeSubDomains",
        "X-Content-Type-Options": "nosniff",
        "X-Frame-Options": "DENY",
        "Timing-Allow-Origin": "*",
        "x-ms-apihub-cached-response": "true",
        "x-ms-apihub-obo": "true",
        "Date": "Thu, 01 Sep 2022 12:59:18 GMT",
        "Content-Length": "588",
        "Content-Type": "application/json",
        "Expires": "-1"
    },
    "body": {
        "error": {
            "code": 502,
            "source": "flow-apim-europe-001-westeurope-01.azure-apim.net",
            "clientRequestId": "14004b95-513c-49ad-a9bb-d890b8e532b0",
            "message": "BadGateway",
            "innerError": {
                "status": 502,
                "message": "The request was aborted: The request was canceled.\r\nclientRequestId: 14004b95-513c-49ad-a9bb-d890b8e532b0",
                "source": "https://sharepointonline-we.azconn-we-003.p.azurewebsites.net/datasets/https%253A%252F%252FTENANT.sharepoint.com%252Fsites%252FBusinessIntelligenceTeam/httprequest",
                "errors": []
            }
        }
    }
}

[chris421]

@Expiscornovus 

So, I spent some time setting up Postman, and all steps were working.....APART from the "Upload file". I kept getting a socket hang up error, and nothing was happening - and that was using the JSON driveItem as the raw body of the PUT request. 

Then, I swap to a binary body, and directly attach the file....and it works first time -- file works fine, and is sitting in exactly the folder in the correct SPO site....

{
    "@odata.context": "https://TENANT.sharepoint.com/sites/BusinessIntelligenceTeam/_api/v2.0/$metadata#items/$entity",
    "@content.downloadUrl": "https://TENANT.sharepoint.com/sites/BusinessIntelligenceTeam/_layouts/15/download.aspx?UniqueId=745ec5df-1d2f-4ff2-abb1-7cfd0a8e3874&Translate=false&tempauth=eyJ0eXAiOiJKV1QiLCJhbGciOiJub25lIn0.eyJhdWQiOiIwMDAwMDAwMy0wMDAwLTBmZjEtY2UwMC0wMDAwMDAwMDAwMDAvc2NvdHJhaWwuc2hhcmVwb2ludC5jb21ANmFlNjE0MWUtMTMyMy00ZTdlLThhMTEtY2RkOThjNjJkODhhIiwiaXNzIjoiMDAwMDAwMDMtMDAwMC0wZmYxLWNlMDAtMDAwMDAwMDAwMDAwIiwibmJmIjoiMTY2MjEwNTcwMiIsImV4cCI6IjE2NjIxMDkzMDIiLCJlbmRwb2ludHVybCI6IjBqU3V3UUx5SmpZR085Z1A5Q2RRMU94b2pjS25hb3J3OEdvcUxoM052K1E9IiwiZW5kcG9pbnR1cmxMZW5ndGgiOiIxNTAiLCJpc2xvb3BiYWNrIjoiVHJ1ZSIsImNpZCI6Ik5USm1Oall3WVRBdE9EQTBOUzAwTURBd0xXWTNOakF0T0ABCDEFGHOV0V3WVdGaCIsInZlciI6Imhhc2hlZHByb29mdG9rZW4iLCJzaXRlaWQiOiJZelZqTnpCaE4ySXRZamN3TWkwME5HUXlMVGhqTWpNdFltSm1aR0ZoTVRCaE9UazMiLCJhcHBfZGlzcGxheW5hbWUiOiJQb3dlckF1dG9tYXRlIiwibmFtZWlkIjoiYTgyNmJkZGEtZjBhYy00NWE0LWE3MTEtNjM2YWEyMDk0MjAwQDZhZTYxNDFlLTEzMjMtNGU3ZS04YTExLWNkZDk4YzYyZDg4YSIsInJvbGVzIjoiZ3JvdXAucmVhZCBhbGxmaWxlcy53cml0ZSBhbGxzaXRlcy53cml0ZSBhbGxwcm9maWxlcy53cml0ZSBhbGxwcm9maWxlcy5yZWFkIiwidHQiOiIxIiwidXNlUGVyc2lzdGVudENvb2tpZSI6bnVsbCwiaXBhZGRyIjoiMTY1LjIyNS4xOTcuNTEifQ.alQ0V1R2d2g2ZVZtcGRPck9tcEhtWURnODdhQzRmaUlPdWhFblFFQlVidz0&ApiVersion=2.0",
    "createdBy": {
        "application": {
            "id": "a826bdda-f0ac-45a4-a711-636aa2094200",
            "displayName": "PowerAutomate"
        },
        "user": {
            "displayName": "SharePoint App"
        }
    },
    "createdDateTime": "2022-09-01T14:51:27Z",
    "eTag": "\"{745EC5DF-1D2F-4FF2-ABB1-7CFD0A8E3874},3\"",
    "id": "01MK5OREW7YVPHIFGHJJH2XML47UFI4ODU",
    "lastModifiedBy": {
        "application": {
            "id": "a826bdda-f0ac-45a4-a711-636aa2094200",
            "displayName": "PowerAutomate"
        },
        "user": {
            "displayName": "SharePoint App"
        }
    },
    "lastModifiedDateTime": "2022-09-02T08:01:42Z",
    "name": "CELA_Licenses_Public_Use_Icons_Chris.pdf",
    "parentReference": {
        "driveType": "documentLibrary",
        "driveId": "b!ewrHxQK30kSMI7v9qhCpl3_TUT-MUG1Bssx9-NG9oM-e3FZSvVdEQ7X1IsmVo6b9",
        "id": "01MK5ORERBHCW67UADSDFGZVD7TPFD33O7R",
        "path": "/drive/root:/General/Requests/2022/Commerical/project"
    },
    "webUrl": "https://TENANT.sharepoint.com/sites/BusinessIntelligenceTeam/Shared%20Documents/General/Requests/2022/Commerical/project/CELA_Licenses_Public_Use_Icons_Chris.pdf",
    "cTag": "\"c:{745EC5DF-1D2F-4FF2-ABB1-7CFD0A8E3874},2\"",
    "file": {
        "hashes": {
            "quickXorHash": "QtZKX8GoC1J+bEgdcunEdX+50B4="
        },
        "irmEnabled": false,
        "mimeType": "application/pdf"
    },
    "fileSystemInfo": {
        "createdDateTime": "2022-09-01T14:51:27Z",
        "lastModifiedDateTime": "2022-09-02T08:01:42Z"
    },
    "size": 65043
}

So....now I'm thinking it's something to do with the driveItem that I'm attaching in PowerAutomate?