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
@@ -20,19 +20,19 @@ To use the sample below, you must substitute the ID of the Flow you want to run.
20
20
21
21
To obtain the ID of a flow that is solution-aware:
22
22
23
-
1.Choose Flow > See your flows in the SharePoint list where the Flow is configured.
24
-
2. If applicable, [switch to the environment](/power-platform/admin/working-with-environments#switch-the-environment) in which the Flow is hosted.
25
-
3. Choose the Solutions area.
26
-
4. Choose the solution in which the Flow was created.
27
-
5. Filter for Cloud flows and select the Flow you want to run.
28
-
6. Choose Export > Get flow identifier.
29
-
7. Copy the ID.
23
+
1.Select **Flow > See your flows** in the SharePoint list where the Flow is configured.
24
+
1. If applicable, [switch to the environment](/power-platform/admin/working-with-environments#switch-the-environment) in which the Flow is hosted.
25
+
1. Select the Solutions area.
26
+
1. Select the solution in which the Flow was created.
27
+
1. Filter for Cloud flows and select the Flow you want to run.
28
+
1. Select Export > Get flow identifier.
29
+
1. Copy the ID.
30
30
31
31
To obtain the ID of a flow that is not solution-aware:
32
32
33
-
1.Choose Flow > See your flows in the SharePoint list where the Flow is configured.
34
-
2. Choose the Flow you want to run.
35
-
3. Copy the ID from the end of the URL.
33
+
1.Select **Flow > See your flows** in the SharePoint list where the Flow is configured.
34
+
1. Select the Flow you want to run.
35
+
1. Copy the ID from the end of the URL.
36
36
37
37
```JSON
38
38
{
@@ -69,92 +69,91 @@ To obtain the ID of a flow that is not solution-aware:
69
69
```
70
70
71
71
Additionally, you can use `headerText` and `runFlowButtonText` options within the `actionParams` property to customize portions of the Flow panel itself! See the [button elements](./formatting-syntax-reference.md#customrowaction) portion of the Detailed syntax reference for more details.
72
-
## Custom cards on hover
72
+
73
+
## Custom cards on hover
73
74
74
75
The following image shows a list with a custom hover added to a List:
75
76
76
-
On hover - Metadata on the column "Status" is made available in view formatting
77
+
On hover - Metadata on the column "Status" is made available in view formatting:
77
78
78
79
79
80
80
-
On hover - Metadata on the column "Status" is made available in column formatting
81
+
On hover - Metadata on the column "Status" is made available in column formatting:
81
82
82
83
83
84
85
+
You can use formatting to define custom call out that can be commissioned basis user defined actions like click or hover.
84
86
85
-
86
-
You can use formatting to define custom call out that can be commissioned basis user defined actions like click or hover
87
-
88
-
This example uses customCardProps, openOnEvent, directionalHint and isBeakVisible
87
+
This example uses `customCardProps`, `openOnEvent`, `directionalHint` and `isBeakVisible`:
89
88
90
89
```JSON
91
90
{
92
-
"elmType": "div",
93
-
"style": {
94
-
"font-size": "12px"
91
+
"elmType": "div",
92
+
"style": {
93
+
"font-size": "12px"
94
+
},
95
+
"txtContent": "[$Status]",
96
+
"customCardProps": {
97
+
"formatter": {
98
+
"elmType": "div",
99
+
"txtContent": "Define your formatter options inside the customCarProps/formatter property"
95
100
},
96
-
"txtContent": "[$Status]",
97
-
"customCardProps": {
98
-
"formatter": {
99
-
"elmType": "div",
100
-
"txtContent": "Define your formatter options inside the customCarProps/formatter property"
101
-
},
102
-
"openOnEvent": "hover",
103
-
"directionalHint": "bottomCenter",
104
-
"isBeakVisible": true,
105
-
"beakStyle" : {
106
-
"backgroundColor": "white"
107
-
}
101
+
"openOnEvent": "hover",
102
+
"directionalHint": "bottomCenter",
103
+
"isBeakVisible": true,
104
+
"beakStyle" : {
105
+
"backgroundColor": "white"
108
106
}
107
+
}
109
108
}
110
109
```
111
110
112
111
## Default cards on hover
113
112
114
-
Users can now have profile card or file hover card on formatters too, some of the things users can now do -
115
-
1) Profile card or File Hover card on any column
116
-
2) Profile card or Hover card with view formatting
113
+
Users can now have profile card or file hover card on formatters too, some of the things users can now do:
117
114
118
-
Hover on a filename with formatting with default file card
115
+
1. Profile card or File Hover card on any column
116
+
1. Profile card or Hover card with view formatting
119
117
120
-
118
+
Hover on a filename with formatting with default file card:
121
119
120
+
122
121
123
-
Hover on a person column with formatting with default Profile card
122
+
Hover on a person column with formatting with default Profile card:
@@ -254,9 +253,10 @@ The following image shows a list with a Gallery layout referencing the Category
254
253
}
255
254
}
256
255
```
256
+
257
257
## Inline Editing
258
258
259
-
With inline editing, formatters have the ability to load field editors to edit field data on an item.
259
+
With inline editing, formatters have the ability to load field editors to edit field data on an item.
260
260
Users need to have edit permissions on the list item and the field type should belong to set of supported types for this feature to work.
261
261
262
262
A special json property `inlineEditField` is used with value as the field internal name __`[$FieldName]`__ at the target element in the json.
@@ -268,14 +268,15 @@ A special json property `inlineEditField` is used with value as the field intern
268
268
"txtContent": "[$FieldName]"
269
269
}
270
270
```
271
-
<br />
272
271
273
272
274
273
275
274
This allows the users to edit items in-place, within the view, without navigating away to grid based editing or to a item edit form.
276
275
277
276
### Supported Field Types
278
-
List of supported field types for inline editing
277
+
278
+
List of supported field types for inline editing:
279
+
279
280
- Single line text
280
281
- Multi line text (without RTF)
281
282
- Number
@@ -285,7 +286,8 @@ List of supported field types for inline editing
285
286
- Lookup
286
287
287
288
### Hover Borders and Customizations
288
-
The inline editing adds a hover border on the elements to indicate these elements have an associated action. The default border is `neutralSecondary` , and on click, the editor appears with a `themePrimary` border. These border colors can be overriden via setting style on the same element with `inlineEditField` by using some special attributes - `--inline-editor-border-width`, `--inline-editor-border-style`, `--inline-editor-border-radius` and `--inline-editor-border-color`.
289
+
290
+
The inline editing adds a hover border on the elements to indicate these elements have an associated action. The default border is `neutralSecondary` , and on click, the editor appears with a `themePrimary` border. These border colors can be overriden via setting style on the same element with `inlineEditField` by using some special attributes - `--inline-editor-border-width`, `--inline-editor-border-style`, `--inline-editor-border-radius`, and `--inline-editor-border-color`.
289
291
290
292
```json
291
293
{
@@ -303,9 +305,9 @@ The inline editing adds a hover border on the elements to indicate these element
303
305
304
306
## Set multiple field values of an Item using customRowAction
305
307
306
-
With the new `setValue``customRowAction`, formatters can render action buttons which modify the item internally without opening editors or forms. `setValue` also allows setting multiple field values of the item at once.
308
+
With the new `setValue`and `customRowAction` properties, formatters can render action buttons which modify the item internally without opening editors or forms. `setValue` also allows setting multiple field values of the item at once.
307
309
308
-
The below JSON will set value of `FieldInternalName_1`, `FieldInternalName_2` and `FieldInternalName_3`with the values provided.
310
+
The below JSON will set value of `FieldInternalName_1`, `FieldInternalName_2`, and `FieldInternalName_3`with the values provided:
309
311
310
312
```json
311
313
{
@@ -323,37 +325,47 @@ The below JSON will set value of `FieldInternalName_1`, `FieldInternalName_2` an
323
325
```
324
326
325
327
### Supported Field Types
328
+
326
329
- Single line text
327
330
- Multi line text (without RTF)
328
331
- Number
329
332
- DateTime
330
333
- Choice and MultiChoice
331
334
- User and Multi user
332
335
333
-
### Value Field values in `actionInput` :
334
-
- Text values:
335
-
- a valid string like `"Choice 1"`
336
-
- value from other columns : `[$ColumnName]`
337
-
- an [expression](./formatting-syntax-reference.md#expressions) like <br>
0 commit comments