Merge branch 'main' into ewehrle-TOC-edit

Author: EllenWehrle

.openpublishing.redirection.json

@@ -8710,6 +8710,11 @@
       "redirect_url": "/power-pages/templates/dynamics-365-apps/overview",
       "redirect_document_id": false
     },
+    {
+      "source_path": "powerapps-docs/maker/portals/configure/dataverse-search.md",
+      "redirect_url": "/power-pages/configure/search/overview",
+      "redirect_document_id": false
+    },
     {
       "source_path": "powerapps-docs/maker/portals/create-common-problems.md",
       "redirect_url": "/power-pages/getting-started/create-manage",

powerapps-docs/developer/data-platform/aad-group-team.md

@@ -2,7 +2,7 @@
 title: "Work with Azure Active Directory group teams (Dataverse)| Microsoft Docs"
 description: "Learn about working with an Azure Active Directory group team using the Web API."
 ms.custom: ""
-ms.date: 02/15/2022
+ms.date: 09/21/2023
 
 ms.suite: ""
 ms.tgt_pltfrm: ""
@@ -246,6 +246,10 @@ If you have a non-interactive process where your service needs to check if the u
 
 More information: [Impersonate another user](impersonate-another-user.md)
 
+## Triggering an event when a team member is added or removed from the group team
+
+Group members are added or removed [just-in-time](#just-in-time-updates) into the Dataverse group team using the [associate and disassociate APIs](webapi/associate-disassociate-entities-using-web-api.md). You can register a [plug-in](plug-ins.md) on the event triggered by these team member additions or removals from the group team.
+
 ### See also
 
 [Manage app and resource access using Azure Active Directory groups](/azure/active-directory/fundamentals/active-directory-manage-groups)

powerapps-docs/developer/data-platform/best-practices/business-logic/implement-all-types-of-queries-when-filtering-preoperation-retrievemultiple.md

@@ -26,7 +26,7 @@ contributors:
 
 ## Symptoms
 
-RetrieveMultiple calls from different application display different results.
+RetrieveMultiple calls from different applications display different results.
 
 - For example: same views in legacy applications show different results in new applications.
 

powerapps-docs/developer/data-platform/org-service/page-large-result-sets-with-fetchxml.md

@@ -18,7 +18,7 @@ You can page the results of a FetchXML query by using the paging cookie. The pag
 
 FetchXML and <xref:Microsoft.Xrm.Sdk.Query.QueryExpression> use different formats for their paging cookies. If you convert from one query format to the other by using the <xref:Microsoft.Crm.Sdk.Messages.FetchXmlToQueryExpressionRequest> message or the <xref:Microsoft.Crm.Sdk.Messages.QueryExpressionToFetchXmlRequest> message, the paging cookie value is ignored. In addition, if you request nonconsecutive pages, the paging cookie value is ignored.  
 
- When you use the paging cookie with FetchXML, make sure that you use the correct encoding. The following example shows the correct encoding when using the paging cookie with FetchXML:  
+ When you use the paging cookie with FetchXML, you must XML encode the cookie value. The following example shows what the XML encoded cookie looks like when using the paging cookie with FetchXML: 
 
 ```csharp  
 strQueryXML = @"  

powerapps-docs/developer/data-platform/user-team-entities.md

@@ -50,7 +50,7 @@ User and team management is the area of Microsoft Dataverse where you can create
 
 To find the user who is currently logged on or who is impersonated, call the <xref:Microsoft.Crm.Sdk.Messages.WhoAmIRequest> message.  
 
-### Delete a user (preview)
+### Delete a user
 
  In Dataverse, users can be disabled and deleted. You can delete a user from Power Platform (Dataverse) assuming you have the required access permission to the [SystemUser table](reference/entities/systemuser.md) row. There is a sequence of tasks to follow. You cannot simply delete the row in a single call. You must first delete the user registered in Microsoft Azure Active Directory (AD) and then delete the user in Dataverse. The procedure to follow is outlined below.
 

powerapps-docs/developer/model-driven-apps/clientapi/reference/Xrm-Navigation/openAlertDialog.md

@@ -3,7 +3,7 @@ title: "openAlertDialog (Client API reference) in model-driven apps| MicrosoftDo
 description: Includes description and supported parameters for the openAlertDialog method.
 author: HemantGaur
 ms.author: hemantg
-ms.date: 03/12/2022
+ms.date: 09/18/2023
 ms.reviewer: jdaly
 ms.topic: reference
 search.audienceType: 
@@ -23,17 +23,19 @@ contributors:
 
 ## Parameters
 
+> [!NOTE]
+> With the *[new look](../../../../../user/modern-fluent-design.md)* enabled, dialog height will resize automatically if you don't set the **height** value of the dialog options.
+
 |Name |Type |Required |Description |
 |---|---|---|---|
-|alertStrings|Object|Yes|The strings to be used in the alert dialog. The object contains the following values:<br/>- **confirmButtonLabel**: (Optional) String. The confirm button label. If you do not specify the button label, **OK** is used as the button label.<br/>- **text**: String. The message to be displayed in the alert dialog.<br/>- **title**: (Optional) String. The title of the alert dialog.|
-|alertOptions|Object|No|The height and width options for alert dialog. The object contains the following values:<br/>- **height**: (Optional) Number. Height of the alert dialog in pixels.<br/>- **width**: (Optional) Number. Width of the alert dialog pixels.|
-|successCallback|function|No|A function to execute when the alert dialog is closed by either clicking the confirm button or canceled by pressing ESC.|
+|alertStrings|Object|Yes|The strings to be used in the alert dialog. The object contains the following values:<br/>- **confirmButtonLabel**: (Optional) String. The confirm button label. If you don't specify the button label, **OK** is used as the button label.<br/>- **text**: String. The message to be displayed in the alert dialog.<br/>- **title**: (Optional) String. The title of the alert dialog.|
+|alertOptions|Object|No|The height and width options for alert dialog. The object contains the following values:<br/>- **height**: (Optional) Number. Height of the alert dialog in pixels.<br/>- **width**: (Optional) Number. Width of the alert dialog pixels.<br><br> With the *[new look](../../../../../user/modern-fluent-design.md)* enabled, dialog height resizes automatically if you don't set the **height** value of the dialog options.|
+|successCallback|function|No|A function to execute when the alert dialog closes either clicking the confirm button or canceled by pressing ESC.|
 |errorCallback|function|No|A function to execute when the operation fails.|
 
-
 ## Example
 
-The following sample code displays an alert dialog. Clicking **Yes** button in the alert dialog or canceling the alert dialog by pressing ESC calls the `close` function::
+The following sample code displays an alert dialog. Clicking **Yes** button in the alert dialog or canceling the alert dialog by pressing ESC calls the `close` function:
 
 ```JavaScript
 var alertStrings = { confirmButtonLabel: "Yes", text: "This is an alert.", title: "Sample title" };
@@ -48,7 +50,7 @@ Xrm.Navigation.openAlertDialog(alertStrings, alertOptions).then(
 );
 ```
 
-### Related topics
+### Related articles
 
 [Xrm.navigation](../xrm-navigation.md)
 

powerapps-docs/developer/model-driven-apps/clientapi/reference/Xrm-Navigation/openConfirmDialog.md

@@ -3,7 +3,7 @@ title: "openConfirmDialog (Client API reference) in model-driven apps| Microsoft
 description: Includes description and supported parameters for the openConfirmDialog method.
 author: HemantGaur
 ms.author: hemantg
-ms.date: 03/12/2022
+ms.date: 09/18/2023
 ms.reviewer: jdaly
 ms.topic: reference
 applies_to: "Dynamics 365 (online)"
@@ -24,10 +24,15 @@ contributors:
 
 ## Parameters
 
+> [!NOTE]
+> With the *[new look](../../../../../user/modern-fluent-design.md)* enabled, dialog height will resize automatically if you don't set the **height** value of the dialog options.
+
+
+
 |Name |Type |Required |Description |
 |---|---|---|---|
-|confirmStrings|Object|Yes|The strings to be used in the confirmation dialog. The object contains the following values:<br/>- **cancelButtonLabel**: (Optional) String. The cancel button label. If you do not specify the cancel button label, **Cancel** is used as the button label.<br/>- **confirmButtonLabel**: (Optional) String. The confirm button label. If you do not specify the confirm button label, **OK** is used as the button label.<br/>- **subtitle**: (Optional) String. The subtitle to be displayed in the confirmation dialog.<br/>- **text**: String. The message to be displayed in the confirmation dialog.<br/>- **title**: (Optional) String. The title to be displayed in the confirmation dialog.|
-|confirmOptions|Object|No|The height and width options for confirmation dialog. The object contains the following values:<br/>- **height**: (Optional) Number. Height of the confirmation dialog in pixels.<br/>- **width**: (Optional) Number. Width of the confirmation dialog in pixels.|
+|confirmStrings|Object|Yes|The strings to be used in the confirmation dialog. The object contains the following values:<br/>- **cancelButtonLabel**: (Optional) String. The cancel button label. If you don't specify the cancel button label, **Cancel** is used as the button label.<br/>- **confirmButtonLabel**: (Optional) String. The confirm button label. If you don't specify the confirm button label, **OK** is used as the button label.<br/>- **subtitle**: (Optional) String. The subtitle to be displayed in the confirmation dialog.<br/>- **text**: String. The message to be displayed in the confirmation dialog.<br/>- **title**: (Optional) String. The title to be displayed in the confirmation dialog.|
+|confirmOptions|Object|No|The height and width options for confirmation dialog. The object contains the following values:<br/>- **height**: (Optional) Number. Height of the confirmation dialog in pixels.<br/>- **width**: (Optional) Number. Width of the confirmation dialog in pixels. <br><br>With the *[new look](../../../../../user/modern-fluent-design.md)* enabled, dialog height resizes automatically if you don't set the **height** value of the dialog options.|
 |successCallback|function|No|A function to execute when the confirmation dialog is closed by clicking the confirm, cancel, or **X** in the top-right corner of the dialog. An object with the **confirmed** (Boolean) attribute is passed that indicates whether the confirm button was clicked to close the dialog.|
 |errorCallback|function|No|A function to execute when the operation fails.|
 
@@ -48,7 +53,7 @@ function (success) {
 
 ```
 
-### Related topics
+### Related articles
 
 [Xrm.Navigation](../xrm-navigation.md)
 

powerapps-docs/developer/model-driven-apps/clientapi/reference/attributes/setSubmitMode.md

@@ -3,7 +3,7 @@ title: "setSubmitMode (Client API reference)| MicrosoftDocs"
 description: Sets whether data from the column will be submitted when the record is saved. 
 author: HemantGaur
 ms.author: hemantg
-ms.date: 03/12/2022
+ms.date: 09/18/2023
 ms.reviewer: jdaly
 ms.topic: reference
 applies_to: "Dynamics 365 (online)"
@@ -33,9 +33,9 @@ All
 
 **Description**: Set one of the following mode values:
 
-- **always**: The data is always sent with a save.
-- **never**: The data is never sent with a save. When this value is used, the column(s) in the form for this column cannot be edited.
-- **dirty**: Default behavior. The data is sent with the save when it has changed.
+- `always`: The data is always sent with a save.
+- `never`: The data is never sent with a save. When this value is used, the column(s) in the form for this column cannot be edited.
+- `dirty`: Default behavior. The data is sent with the save when it has changed.
 
 ## Remarks
 
@@ -44,7 +44,7 @@ Use this method to control when data for a column is submitted when a record is
 > [!NOTE]
 > Data in a column will always be refreshed after save operation, even if the column's submit mode is set to `never`. For example, if a column's value in the server is null and the column's submit mode is set to `never`, and the column is modified with some value by the user, after the user saves the form the column's value will be replaced with null.
 
-Columns that do not get updated after the initial save of the record, such as **createdby**, are set so that they will not be submitted on save. To force a column value to be submitted whether it has changed or not, use this method with the *mode* parameter set to "always".
+Columns that do not get updated after the initial save of the record, such as `createdby`, are set so that they will not be submitted on save. To force a column value to be submitted whether it has changed or not, use this method with the `mode` parameter set to `always`.
 
 ### See also
 [getSubmitMode (Client API reference)](getSubmitMode.md)

powerapps-docs/developer/model-driven-apps/clientapi/send-in-app-notifications.md

@@ -1119,12 +1119,13 @@ In addition to the appropriate table permissions, a user must be assigned the **
 |Usage|Required table privileges|
 |------------|----------------|
 |User has no in-app notification bell and receives no in-app notification |None: Read privilege on the app notification table. |
-|User can receive in-app notifications|<ul><li>Basic: Read privilege on the app notification table.</li><li>Create, Read, Write, and Append privileges on the model-driven app user setting.</li><li>Read privileges on setting definition.</li></ul> |
+|User can receive in-app notifications|<ul><li>Basic: Read privilege on the app notification table.</li><li>Create, Read, Write, and Append privileges on the model-driven app user setting.</li><li>Read and AppendTo privileges on setting definition.</li></ul> |
 |User can send in-app notifications to self |Basic: Create and Read privileges on the app notification table, and Send In-App Notification privilege. |
 |User can send in-app notifications to others |Read privilege with Local, Deep, or Global access level on the app notification table based on the receiving user's business unit, and Send In-App Notification privilege. |
 | User can delete in-app notifications | Global: Delete privileges on the app notification table. |
 
 
+
 ## Notification storage
 
 Because the app notification table uses the organization's database storage capacity, it's important to consider the volume of notifications sent and the expiration setting. More information: [Microsoft Dataverse storage capacity](/power-platform/admin/capacity-storage)

powerapps-docs/developer/test-engine/overview.md

@@ -87,7 +87,7 @@ $env:user1Password = "fake password"
 
 ### Run the test
 
-Use the PAC CLI [pac tests run](/power-platform/developer/cli/reference/tests#pac-tests-run) command to run your test plan. You must provide:
+Use the PAC CLI [pac test run](/power-platform/developer/cli/reference/tests#pac-test-run) command to run your test plan. You must provide:
 
 - Path to your test plan file
 - EnvironmentId