Microsoft GraphUpload large file
BetaChanges data
Sends a Storage file to a OneDrive or SharePoint folder in parts.
Settings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Microsoft Graph connection the step signs in with. |
| Drive of | "user" or "group" or "site" or "drive" |
| OwnerRequired | The person's id or sign-in address, the group's id, the site's id or the drive's id — whichever Drive of names. |
| Folder | The folder's id, or its path from the drive's root starting with /. Leave empty for the root. |
| Storage fileRequired | A file's name is the whole key — exports/report.csv is a name, not a folder. It is sent in 5 MB parts, so the run's file bound limits it — Storage holds up to 100 MB per file — not Microsoft Graph's. |
| File name | The name in the folder. Leave empty for the Storage name after its last /. |
| If the name is taken | "replace" or "rename" or "fail" |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `microsoft-graph`) |
driveOf | "user" or "group" or "site" or "drive", by default "user" |
owner | text |
folder | text |
file | texta file name, listed in `requires.files` |
name | text |
conflictBehavior | "replace" or "rename" or "fail", by default "replace" |
Output
| Field | Type |
|---|---|
idFile id | string |
webUrlLink in Microsoft 365 | string |
itemFile | object |
Sample output, and the expression for each field
- id"01BIG"
- item
- id"01BIG"
- webUrl"https://contoso.sharepoint.com/dump"
Errors
When a step of this node stops a run, the run page shows a code. Look it up:
Example step
The step as a flow file holds it. Replace each value in <…>.
{
"config": {
"conflictBehavior": "replace",
"connection": "<connection id>",
"driveOf": "user",
"file": "<storage file>",
"folder": "",
"name": "",
"owner": "<owner>"
},
"label": "Upload large file",
"type": "graph.uploadLargeFile",
"version": 1
}