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/introduction-to-sharepoint-business-process-integration.md
+21-2Lines changed: 21 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -7,13 +7,15 @@ localization_priority: Priority
7
7
---
8
8
9
9
# Business apps and business process automation
10
+
Creativity and teamwork are essential to transforming business processes. Most processes center on content – files and data. SharePoint offers tools to gather and manage data in lists and libraries.
10
11
11
-
Creativity and teamwork are essential to transforming business process. Most processes center on content – files and data. SharePoint gives you tools to gather and manage data in lists and libraries.
12
12
13
13
Microsoft 365 provides connections to a range of third-party systems with Power Automate and Power Apps. Power Automate lets you automate business processes, and Power Apps lets you create great forms and mobile apps based on SharePoint files and data. Both Power Autoamte and Power Apps feature intuitive visual designers, so anyone can craft forms and screens using a convenient interface.
14
14
15
15
## Automate business processes
16
+
Office 365 provides connections to a range of third-party systems with Power Automate and Power Apps. Power Automate lets you easily automate business processes while Power Apps lets you create exceptional forms and mobile apps based on SharePoint files and data. Both Power Automate and Power Apps feature intuitive visual designers, so anyone can build forms and screens in an easy-to-use interface.
16
17
18
+
## Power Automate
17
19
Using Power Automate, you can create workflows through an easy-to-use visual designer that will guide you through each step and help authenticate your accounts.
18
20
19
21
Select from dozens of pre-made templates to start automating your app’s usage. Here are just a few applications of these templates:
@@ -24,12 +26,12 @@ Select from dozens of pre-made templates to start automating your app’s usage.
24
26
* Create a new item in SharePoint when a new order is added in Salesforce.
25
27
* Route finished documents to a team for approval.
26
28
29
+
27
30
Whether you start with a template or begin from scratch, using Power Automate to create automation features is intuitive.
28
31
29
32
Cross-tool functionality seamlessly moves your data from one operation to another. SharePoint is a core piece of the Microsoft 365 suite integrating your data seamlessly with tools like Excel or Power BI reporting. And because it uses an Excel-inspired expression language, these tools communicate with each other, using formula language you already recognize to integrate your data from one function to the next.
30
33
31
34
## Build business apps
32
-
33
35
Using Microsoft Power Apps, you can create apps with a point-and-click approach to app design. You can use the option to use automatically generated pre-made templates, or customize the tool to fit your more specific needs. After your app is complete, you can instantly publish it to Windows, the web, iOS, and Android.
34
36
35
37
Classic mobile and web apps typically required separate coding for each platform, which can be costly and time-consuming to do—especially since developers are in such high demand. Instead, Power Apps simplifies the process so anyone can do it. Its simple, browser-based visual designer helps you rapidly build custom business apps without having to write any code.
@@ -41,6 +43,23 @@ Power Apps also lets you to easily customize the form for a SharePoint list. Wit
41
43
* Show or hide certain fields.
42
44
* Re-organize those fields.
43
45
* Change the layout of the form.
46
+
47
+
Whether you start with a template or begin from scratch, using Power Automate to create automation features is intuitive and easy to understand.
48
+
49
+
Cross-tool functionality seamlessly moves your data from one operation to another. With SharePoint being a core component of the Microsoft 365 suite, your data easily integrates with tools like Excel or Power BI reporting. And because it uses an Excel-inspired expression language, these tools talk with each other, using formula language you already recognize and understand to integrate your data from one function to the next.
50
+
51
+
## Power Apps
52
+
Using Power Apps, you can create apps with a point-and-click approach to app design. Options include using automatically-generated, pre-made templates, or customizing the tool to fit your more specific needs. After your app is complete, you can instantly publish it to Windows, the web, iOS, and Android.
53
+
54
+
Classic mobile and web apps typically required separate coding for each platform, which can be costly and time-consuming to do—especially with developers in high demand. Instead, Power Apps simplifies the process so anyone can do it. Its easy-to-use, browser-based visual designer helps you rapidly build custom business apps without having to write any code.
55
+
56
+
By connecting Power Apps to your existing systems and data, you can quickly build reports, forms, and workflows, and then publish your app instantly to all users in your organization.
57
+
58
+
Power Apps also lets you easily customize the form for a SharePoint list. For example, with custom forms, you can:
59
+
60
+
* Show or hide certain fields.
61
+
* Reorganize those fields.
62
+
* Change the layout of a form.
44
63
* Add formatted text and graphics.
45
64
46
65
When you publish your changes, the form is embedded within the SharePoint list for use by all of its users.
Copy file name to clipboardExpand all lines: docs/business-apps/power-automate/get-started/sharepoint-actions-triggers.md
+31-31Lines changed: 31 additions & 31 deletions
Original file line number
Diff line number
Diff line change
@@ -3,51 +3,51 @@ title: Microsoft SharePoint Connector for Power Automate
3
3
ms.date: 03/13/2020
4
4
---
5
5
6
-
# Microsoft SharePoint Connector for Power Automate
6
+
# Microsoft SharePoint Connector in Power Automate
7
7
8
8
Microsoft SharePoint Connector in Power Automate supports the following flow triggers and actions.
9
9
10
10
## SharePoint triggers
11
11
12
12
### When an item is created
13
13
14
-
Triggers the flow when an item is created.
14
+
Triggers the flow when you create an item in a SharePoint list.
15
15
16
16
### When an item is created or modified
17
17
18
-
Triggers the flow when an item is created, and each time it is modified, in a SharePoint list.
18
+
Triggers the flow when you create an item, and each time you modify it in a SharePoint list.
19
19
20
20
### When an item is deleted
21
21
22
-
Triggers the flow when an item is deleted in a list. To get the properties of a deleted item, this trigger must connect to the associated SharePoint site on which it is expected to run using a site collection user account.
22
+
Triggers the flow when you delete an item in a list. To get the properties of a deleted item, you must connect this trigger must to the associated SharePoint site on which it is expected to run, using a site collection user account.
23
23
24
24
### For a selected item
25
25
26
-
Triggers the flow for a selected item in a list.
26
+
Triggers the flow when you select an item in a list.
27
27
28
28
### When a file is created (properties only)
29
29
30
-
Triggers the flow when a file is created in a document library, and returns only the custom file properties associated with that file.
30
+
Triggers the flow when you create a file in a document library, and returns only the custom file properties associated with that file.
31
31
32
32
### When a file is created in a folder
33
33
34
-
Triggers the flow when a file is created in a SharePoint folder. This trigger does not run if a file is added or updated in a subfolder inside the folder this trigger is operating on. If the flow is required to trigger on subfolders, create different flows for one or more subfolder(s).
34
+
Triggers the flow when you create a file in a SharePoint folder. This trigger does not run if you add or update a file in a subfolder inside the folder this trigger is operating on. If the flow is required to trigger on subfolders, create different flows for one or more subfolder(s).
35
35
36
36
### When a file is created or modified (properties only)
37
37
38
-
Triggers the flow when a file is created, and each time the file properties are modified in a library. Returns only the custom file properties associated with that file.
38
+
Triggers the flow when you create a file, and each time you modify the file properties in a library. Returns only the custom file properties associated with that file.
39
39
40
40
### When a file is created or modified in a folder (properties only)
41
41
42
-
Triggers the flow when a file is created, and each time the file properties are modified in the selected SharePoint folder. The trigger does not activate if a file is added/updated in a subfolder. If the flow is required to trigger on subfolders, create different flows for one or more subfolder(s).
42
+
Triggers the flow when you create a file, and each time you modify the file properties in the selected SharePoint folder. The trigger does not activate if you add or update a file in a subfolder. If the flow is required to trigger on subfolders, create different flows for one or more subfolder(s).
43
43
44
44
### When a file is deleted
45
45
46
-
Triggers the flow when a file is deleted in a document library. You can optionally specify a folder to watch. When a folder is deleted, the trigger activates only once for the deleted folder, including its subfolders. To get the properties of the deleted file, this trigger must connect to the associated SharePoint site on which the trigger is epxected to run using a site collection user account.
46
+
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.
47
47
48
48
### For a selected file
49
49
50
-
Triggers the flow for a selected file in a document library.
50
+
Triggers the flow for a file you select in a document library.
51
51
52
52
### When a site has requested to join a hub site
53
53
@@ -61,11 +61,11 @@ Adds a new attachment to the specified list item.
61
61
62
62
### Approve hub site join request
63
63
64
-
Approves hub site join request. This action returns an approval token to complete the join request using the join hub site action.
64
+
Approves hub site join request. This action returns an approval token to complete the join request, using the join hub site action.
65
65
66
66
### Cancel hub site join request
67
67
68
-
Cancels hub join request. If applicable, specify the same Approval Correlation Id as used in the "Set hub site join status to pending" action.
68
+
Cancels hub join request. If applicable, specify the same Approval Correlation Id as used in the **Set hub site join status to pending** action.
69
69
70
70
### Check in file
71
71
@@ -77,15 +77,15 @@ Checks out a file in a document library to prevent others from editing the docum
77
77
78
78
### Copy file
79
79
80
-
Copies a file. Works similarly to the "Copy to" command in SharePoint libraries. Returns info about the new file after copying.
80
+
Copies a file. Works similarly to the **Copy to** command in SharePoint libraries. After copying, returns info about the new file.
81
81
82
82
### Copy file (deprecated)
83
83
84
84
Copies a file to a SharePoint site.
85
85
86
86
### Copy folder
87
87
88
-
Copies a folder. Works similarly to the "Copy to" command in SharePoint libraries. Returns info about the new folder after copying.
88
+
Copies a folder. Works similarly to the **Copy to** command in SharePoint libraries. After copying, returns info about the new folder.
89
89
90
90
### Create file
91
91
@@ -117,7 +117,7 @@ Deletes an item from a SharePoint list.
117
117
118
118
### Discard checkout
119
119
120
-
Discards the checkout, rather than saves the file, if you check out a file and don't make changes to it, or you make changes that you don't want to keep. If your organization tracks versions, a new version is created each time you check a file back into the library. By discarding the checkout, you can avoid making new versions when you haven't made any changes to the file.
120
+
Discards the checkout, rather than saves the file, if you check out a file and don't make changes to it, or you make changes that you don't want to keep. If your organization tracks versions, a new version is created each time you check in a file to the library. By discarding the checkout, you can avoid making new versions when you haven't made any changes to the file.
121
121
122
122
### Extract folder
123
123
@@ -129,47 +129,47 @@ Gets all lists and libraries.
129
129
130
130
### Get attachment content
131
131
132
-
Returns file contents using the file identifier. The contents can be copied somewhere else, or be used as an attachment.
132
+
Returns file contents, using the file identifier. The contents can be copied somewhere else, or be used as an attachment.
133
133
134
134
### Get attachments
135
135
136
-
Returns the list of attachments for the specified list item. To get to the contents of the file, add a "Get attachment content" step, and use the "File identifier" property returned by this action.
136
+
Returns the list of attachments for the specified list item. To get to the contents of the file, add a **Get attachment content** step, and use the **File identifier** property returned by this action.
137
137
138
138
### Get file content
139
139
140
-
Gets file contents using the file identifier. The contents can be copied somewhere else, or be used as an attachment.
140
+
Gets file contents using the file identifier. You can copy the contents somewhere else, or use it as an attachment.
141
141
142
142
### Get file content using path
143
143
144
-
Gets file contents using the file path.
144
+
Gets file contents, using the file path.
145
145
146
146
### Get file metadata
147
147
148
-
Gets info about the file, such as size, etag, created date, and so on. Uses a file identifier to pick the file. To get to the values stored in the columns in the library, use "Get file properties" action.
148
+
Gets info about the file, such as size, etag, created date, and so on. Uses a file identifier to select the file. To get to the values stored in the columns in the library, use the **Get file properties** action.
149
149
150
150
### Get file metadata using path
151
151
152
-
Gets info about the file, such as size, etag, created date, and so on. Uses a file path to pick the file. To get to the values stored in the columns in the library, use "Get file properties" action.
152
+
Gets info about the file, such as size, etag, created date, and so on. Uses a file path to select the file. To get to the values stored in the columns in the library, use the **Get file properties** action.
153
153
154
154
### Get file properties
155
155
156
156
Gets the properties saved in the columns in the library for the item specified by the item id. To get to the contents of the file, add a "Get file content" step, and use the "File identifier" property returned by this action. When using this with the On-Premises Data Gateway, you may need to manually enter the name of the library to connect to.
157
157
158
158
### Get files (properties only)
159
159
160
-
Gets the properties saved in the columns in the library for all folders and files stored in the library. You can also filter down to the items that match a condition. Use "Apply to each" section to work with the output from this action. When using this with the On-Premises Data Gateway, you may need to be manually enter the name of the library to connect to.
160
+
Gets the properties saved in the columns in the library for all folders and files stored in the library. You can also filter down to the items that match a condition. To work with the output from this action, use the **Apply to each** section. When using this with the On-Premises Data Gateway, you may need to be manually enter the name of the library to connect to.
161
161
162
162
### Get folder metadata
163
163
164
-
Gets info about the folder. Uses a file identifier to pick the folder.
164
+
Gets info about the folder. Uses a file identifier to select the folder.
165
165
166
166
### Get folder metadata using path
167
167
168
-
Gets info about the folder. Uses a folder path to pick the folder.
168
+
Gets info about the folder. Uses a folder path to select the folder.
169
169
170
170
### Get item
171
171
172
-
Gets a single item by its id from a SharePoint list.
172
+
Gets a single item by its ID from a SharePoint list.
173
173
174
174
### Get items
175
175
@@ -189,7 +189,7 @@ Grants access to an item or a folder in SharePoint to specific people.
189
189
190
190
### Join hub site
191
191
192
-
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.
192
+
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.
193
193
194
194
### List folder
195
195
@@ -201,19 +201,19 @@ Returns files in the root SharePoint folder.
201
201
202
202
### Move file
203
203
204
-
Moves a file. Works similarly to the "Move to" command in SharePoint libraries. Returns info about the new file after its move.
204
+
Moves a file. Works similarly to the **Move to** command in SharePoint libraries. Returns info about the new file after its move.
205
205
206
206
### Move folder
207
207
208
-
Moves a folder. Works similarly to the "Move to" command in SharePoint libraries. Returns info about the new folder after its move.
208
+
Moves a folder. Works similarly to the **Move to** command in SharePoint libraries. Returns info about the new folder after its move.
209
209
210
210
### Resolve person
211
211
212
212
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.
213
213
214
214
### Send an HTTP request to SharePoint
215
215
216
-
Constructs a SharePoint REST API to invoke. Note: This action may execute any SharePoint REST API you have access to. Proceed with caution.
216
+
Constructs a SharePoint REST API to invoke. **Note**: This action may execute any SharePoint REST API you have access to. Proceed with caution.
217
217
218
218
### Set content approval status
219
219
@@ -233,7 +233,7 @@ Updates the contents of the file specified by the file identifier.
233
233
234
234
### Update file properties
235
235
236
-
Updates the properties stored in columns in a library for the item specified by the item id. To update file contents, use the "Update file" action. When using this with the On-Premises Data Gateway, you may need to manually enter the name of the library to connect to.
236
+
Updates the properties stored in columns in a library for the item specified by the item ID. To update file contents, use the **Update file** action. When using this with the On-Premises Data Gateway, you may need to manually enter the name of the library to connect to.
0 commit comments