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/documentation/docs/controls/DynamicForm.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,6 +61,7 @@ The `DynamicForm` can be configured with the following properties:
61
61
| webAbsoluteUrl | string | no | Absolute Web Url of target site (user requires permissions). |
62
62
| fieldOverrides | {[columnInternalName: string] : {(fieldProperties: IDynamicFieldProps): React.ReactElement\<IDynamicFieldProps\>}} | no | Key value pair for fields you want to override. Key is the internal field name, value is the function to be called for the custom element to render. |
63
63
| respectEtag | boolean | no | Specifies if the form should respect the ETag of the item. Default - `true`|
64
+
| saveDisabled | boolean | no | Specifies if save button is disabled. |
| customIcons | { [ columnInternalName: string ]: string } | no | Specifies custom icons for the form. The key of this dictionary is the column internal name, the value is the Fluent UI icon name. |
Sometimes, depending on how your organization is configured regarding users and groups, performing search can be tricky. As the `PeoplePicker` is using the `SP.UI.ApplicationPages.ClientPeoplePickerWebServiceInterface.clientPeoplePickerSearchUser` endpoint under the hood, there is an optional parameter called `useSubstrateSearch`. Setting this to `true` will perform a search using the Microsoft 365 Substrate, which will go through centralized stored data in order to find requested info. More details about this feature can be found [here](https://techcommunity.microsoft.com/t5/video-hub/admin-39-s-guide-to-the-microsoft-365-substrate/ba-p/3633132) and [here](https://youtu.be/uuiTR8r27Os?si=JkPyfiQggvCMj0xg&t=467).
@@ -66,8 +70,8 @@ The People picker control can be configured with the following properties:
66
70
|----|----|----|----|----|
67
71
|context|IPeoplePickerContext|yes|Contextofthecomponent, based on the SPFx context ([*BaseComponentContext*](https://learn.microsoft.com/javascript/api/sp-component-base/basecomponentcontext?view=sp-typescript-latest)). | |
Copy file name to clipboardExpand all lines: docs/documentation/docs/controls/SitePicker.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ The `SitePicker` control can be configured with the following properties:
52
52
| isDesc | boolean | no | Specifies if the list is sorted in descending order. Default: `false`. |
53
53
| label | string | no | Label to use for the control. |
54
54
| limitToCurrentSiteCollection | boolean | no | Specifies if the options should be limited by the current site collections. Taken into consideration if selectionMode is set to `web`. |
55
-
| mode | `'site' | 'web' | 'hub'` | no | Defines what entities are available for selection: site collections, sites, hub sites. Default: `web`. |
55
+
| mode | `'associatedsites' | 'site' | 'web' | 'hub'` | no | Defines what entities are available for selection: site collections, sites, hub sites and sites inside hub. Default: `web`. |
56
56
| multiSelect | boolean | no | Optional mode indicates if multi-choice selections is allowed. Default: `true`. |
0 commit comments