You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/business-apps/power-automate/sharepoint-connector-actions-triggers.md
+10-10Lines changed: 10 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Microsoft SharePoint Connector for Power Automate
3
3
description: In Power Automate, Microsoft SharePoint Connector supports the following flow triggers and actions.
4
-
ms.date: 09/27/2022
4
+
ms.date: 06/22/2023
5
5
ms.service: power-automate
6
6
search.app:
7
7
- Flow
@@ -48,7 +48,7 @@ For more info about when Microsoft Syntex and how it classifies files see: [Intr
48
48
49
49
### When a file is created (properties only)
50
50
51
-
Triggers the flow when you create a file in a document library, and returns only the custom file properties associated with that file.
51
+
Triggers the flow when you create a file in a document library and returns only the custom file properties associated with that file.
52
52
53
53
### When a file is created in a folder [deprecated]
54
54
@@ -70,7 +70,7 @@ Triggers when a file is created, and also each time it is modified in a SharePoi
70
70
71
71
### When a file is deleted
72
72
73
-
Triggers the flow when you delete a file in a document library. You can optionally specify a folder to watch. When you delete a folder, the trigger activates only once for the deleted folder, including its subfolders. To get the properties of the deleted file, you must connect this trigger to the associated SharePoint site on which the trigger is epxected to run, using a site collection user account.
73
+
Triggers the flow when you delete a file in a document library. You can optionally specify a folder to watch. When you delete a folder, the trigger activates only once for the deleted folder, including its subfolders. To get the properties of the deleted file, you must connect this trigger to the associated SharePoint site on which the trigger is expected to run, using a site collection user account.
74
74
75
75
### For a selected file
76
76
@@ -99,7 +99,7 @@ Cancels hub join request. If applicable, specify the same Approval Correlation I
99
99
100
100
### Check in file
101
101
102
-
Checks in a checkedout file in a document library, which makes the version of the document available to others.
102
+
Checks in a checked-out file in a document library, which makes the version of the document available to others.
103
103
104
104
### Check out file
105
105
@@ -172,13 +172,13 @@ Returns the list of attachments for the specified list item. To get to the conte
172
172
173
173
Gets all the columns or file properties changed since and until a specified time interval. To get all the columns changed when an item or a file is modified:
174
174
- Use the _when an item or file is modified_ trigger, and,
175
-
- Use the _Trigger Window Start Token_ & _Trigger Window End Token_ outputs from the _when an item or file is modified_ trigger to infer what columnns changed since last time flow checked for item or file updates.
175
+
- Use the _Trigger Window Start Token_ & _Trigger Window End Token_ outputs from the _when an item or file is modified_ trigger to infer what columns changed since the last time flow checked for item or file updates.
176
176
177
177
For more info about how to use this action, see this tutorial video: [Introducing 'when an item or file modified' trigger and 'Get changes' action](https://youtu.be/AaWB3xlhJdc)
178
178
179
179
> [!NOTE]
180
180
> - The list or library should have versioning configured in order to infer what columns or properties got modified since last change.
181
-
> - Only column changes are suported for lists and libraries.
181
+
> - Only column changes are supported for lists and libraries.
182
182
> - File content changes are not supported.
183
183
> - Attachment changes are not supported.
184
184
> -_Trigger Window Start Token_ & _Trigger Window End Token_ are only available when you use _when an item or file is modified_ trigger.
@@ -237,7 +237,7 @@ Grants access to an item or a folder in SharePoint to specific people.
237
237
238
238
### Join hub site
239
239
240
-
Joins the requested site to the hub site. An Approval Token is required to complete the join successfully, if that hub requires approval. If applicable, specify the same Approval Correlation Id as used in the **Set hub site join status to pending** action.
240
+
Joins the requested site to the hub site. An Approval Token is required to complete the join successfully if that hub requires approval. If applicable, specify the same Approval Correlation Id as used in the **Set hub site join status to pending** action.
241
241
242
242
### List folder
243
243
@@ -257,7 +257,7 @@ Moves a folder. Works similarly to the **Move to** command in SharePoint librari
257
257
258
258
### Resolve person
259
259
260
-
Returns a single matching user value so it can be assigned to a column of type person. If there are no matches, or multiple matches, this action errors out.
260
+
Returns a single matching user value so it can be assigned to a column of type person. If there are no matches or multiple matches, this action errors out.
261
261
262
262
### Send an HTTP request to SharePoint
263
263
@@ -368,9 +368,9 @@ When you build a Power Automate flow to be triggered for an item, or for creatin
368
368
369
369
### Move files and flow runs
370
370
371
-
When you move one or more files from one document library to another, the original file is moved from the source library to the destination library. Moving the file does not alter any custom metadata, including when the file was created and modified. Hence, this action does not trigger any flows for those file updates associated in the library where it was moved.
371
+
When you move one or more files from one document library to another, the original file is moved from the source library to the destination library. Moving the file does not alter any custom metadata, including when the file was created and modified. Hence, this action does not trigger any flows for those file updates associated with the library where it was moved.
372
372
373
-
### Syncing files to your OneDrive for business and SharePoint document libraries
373
+
### Syncing files to your OneDrive for Business and SharePoint document libraries
374
374
375
375
When users sync one or more files from one document library to another, the original file is moved (synced) from your client to the destination library. Syncing the file will not alter any custom metadata including when the file was created and modified. Hence, this action will not trigger any flows for those file syncs in that library or in your OneDrive for business.
0 commit comments