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/declarative-customization/formatting-advanced.md
+50-49Lines changed: 50 additions & 49 deletions
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,20 @@
1
1
---
2
2
title: Advanced formatting concepts
3
3
description: Advanced formatting concepts
4
-
ms.date: 08/24/2022
4
+
ms.date: 07/16/2025
5
5
ms.localizationpriority: high
6
6
---
7
7
# Advanced formatting concepts
8
8
9
-
You can use some of the following features to make your view and column formatting more informationrich and interactable.
9
+
You can use some of the following features to make your view and column formatting more information-rich and interactive.
10
10
11
11
## Create a button to launch a Flow
12
12
13
13
The following screenshot shows a list with a Flow button added to the Action column:
14
14
15
15

16
16
17
-
You can use column formatting to create buttons that, when selected, run Flows on the corresponding list item. For flows that are [solution-aware](/power-automate/overview-solution-flows), the Flow Launch Panel will be displayed after choosing the button and you must select Run Flow to start the flow. For flows that aren't solution-aware, The Flow Launch Panel will be displayed after choosing the button and the Flow will just run.
17
+
You can use column formatting to create buttons that, when selected, run Flows on the corresponding list item. For flows that are [solution-aware](/power-automate/overview-solution-flows), the Flow Launch Panel will be displayed after choosing the button, and you must select Run Flow to start the flow. For flows that aren't solution-aware, the Flow Launch Panel will be displayed after selecting the button, and the Flow will just run.
18
18
19
19
To use the sample below, you must substitute the ID of the Flow you want to run. This ID is contained within the `actionParams` property of the `customRowAction` attribute inside the `button` element.
20
20
@@ -30,43 +30,44 @@ To obtain the ID of a flow that is solution-aware:
30
30
31
31
To obtain the ID of a flow that isn't solution-aware:
32
32
33
-
1.Select **Flow > See your flows**in the SharePoint list where the Flow is configured.
33
+
1.Switch to the environment in which the Flow is hosted.
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
73
@@ -82,9 +83,9 @@ On hover - Metadata on the column "Status" is made available in column formattin
82
83
83
84

84
85
85
-
You can use formatting to define custom call out that can be commissioned basis user-defined actions like click or hover.
86
+
You can use formatting to define a custom callout that can be commissioned user-defined basis, actions like click or hover.
86
87
87
-
This example uses `customCardProps`, `openOnEvent`, `directionalHint` and `isBeakVisible`:
88
+
This example uses `customCardProps`, `openOnEvent`, `directionalHint`, and `isBeakVisible`:
88
89
89
90
```JSON
90
91
{
@@ -110,20 +111,20 @@ This example uses `customCardProps`, `openOnEvent`, `directionalHint` and `isBea
110
111
111
112
## Default cards on hover
112
113
113
-
Users can now have profile card or file hover card on formatters too, some of the things users can now do:
114
+
Users can now have a profile card or a file hover card on formatters too. Some of the things users can now do:
114
115
115
-
1. Profile card or File Hover card on any column
116
-
1. Profile card or Hover card with view formatting
116
+
- Profile card or File Hover card on any column
117
+
- Profile card or Hover card with view formatting
117
118
118
-
Hover on a filename with formatting with default file card:
119
+
Hover on a filename with formatting with the default file card:
119
120
120
121

121
122
122
-
Hover on a person column with formatting with default Profile card:
123
+
Hover on a person column with formatting with the default Profile card:
123
124
124
125

125
126
126
-
Both the example uses defaultHoverField
127
+
This example uses `defaultHoverField`:
127
128
128
129
```JSON
129
130
{
@@ -257,9 +258,9 @@ The following image shows a list with a Gallery layout referencing the Category
257
258
## Inline Editing
258
259
259
260
With inline editing, formatters have the ability to load field editors to edit field data on an item.
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
+
Users need to have edit permissions on the list item, and the field type should belong to a set of supported types for this feature to work.
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.
263
+
A special JSON property `inlineEditField` is used with value as the field internal name __`[$FieldName]`__ at the target element in the JSON.
263
264
264
265
```json
265
266
{
@@ -287,7 +288,7 @@ List of supported field types for inline editing:
287
288
288
289
### Hover Borders and Customizations
289
290
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 overridden 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`.
291
+
The inline editing adds a hover border on the elements to indicate that 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 overridden 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`.
291
292
292
293
```json
293
294
{
@@ -307,7 +308,7 @@ The inline editing adds a hover border on the elements to indicate these element
307
308
308
309
With the new `setValue` and `customRowAction` properties, formatters can render action buttons that modify the item internally without opening editors or forms. `setValue` also allows setting multiple field values of the item at once.
309
310
310
-
The below JSON will set value of `FieldInternalName_1`, `FieldInternalName_2`, and `FieldInternalName_3`with the values provided:
311
+
The below JSON will set the value of `FieldInternalName_1`, `FieldInternalName_2`, and `FieldInternalName_3`with the values provided:
311
312
312
313
```json
313
314
{
@@ -361,15 +362,15 @@ The below JSON will set value of `FieldInternalName_1`, `FieldInternalName_2`, a
361
362
- `addDays` and `addMinutes`, two new functions to support [expressions](./formatting-syntax-reference.md#expressions) like seven days from today
362
363
- an empty string `""` clears the field value
363
364
- Multi-Choice and Multi-Person:
364
-
- Multivalue fields are special, as they need an array value to save multiple values.
365
+
- Multi-value fields are special, as they need an array value to save multiple values.
365
366
- `appendTo`, `removeFrom`, and `replace`, three functions that can operate on multivalue fields.
366
367
- `appendTo([$MultiChoiceField], 'MyValue')`
367
368
- `removeFrom([$MultiUserField], @me)`: removes all occurrences that match the second parameter
368
-
- `replace([$MultiChoiceField], 'Choice 1', 'Choice 3')`: replaces all occurrences of second parameter with third.
369
+
- `replace([$MultiChoiceField], 'Choice 1', 'Choice 3')`: replaces all occurrences of the second parameter with the third.
369
370
- Person field values:
370
371
- user name or email
371
372
- An empty string `""` clears the field value
372
373
- an [expression](./formatting-syntax-reference.md#expressions) which returns these values
373
374
374
-
> [!NOTE]
375
-
> A query runs with the string value provided on people column and the first person in the returned results is used.
375
+
> [!NOTE]
376
+
> A query runs with the string value provided on the people column, and the first person in the returned results is used.
0 commit comments