Merge branch 'main' into u/vilesyk/3034102_theming_doc

Author: JimDaly

powerapps-docs/developer/data-platform/bulk-operations.md

@@ -396,9 +396,6 @@ A key requirement of the bulk operation messages is that organizations must not
 
 - When a single operation message is used, the respective bulk operation event occurs with an [EntityCollection](xref:Microsoft.Xrm.Sdk.EntityCollection) containing a *single* [Entity](xref:Microsoft.Xrm.Sdk.Entity) instance passed in the `Targets` parameter.  You can move any logic that responds to single operation events to the more efficient bulk operation events and the logic is applied for both individual and multiple operations.
 
-   > [!NOTE]
-   > Don't migrate custom logic to the `DeleteMultiple` message until [Known issue: DeleteMultiple plug-ins not invoked for Delete](deletemultiple.md#deletemultiple-plug-ins-not-invoked-for-delete) is resolved.
-
 Before the introduction of bulk operation messages, all custom logic was on the single operation messages. That logic must continue to be applied when client applications use the bulk operation messages. For tables used with high-volume bulk operations, we recommend that you begin to move any synchronous logic from single message events to bulk operation events. If you're introducing new logic, use the bulk operation events rather than the single operation events.
 
 > [!CAUTION]

powerapps-docs/developer/data-platform/deletemultiple.md

@@ -1,7 +1,7 @@
 ---
 title: Use DeleteMultiple (preview)
 description: Learn how to use Delete to delete multiple rows of data in a Microsoft Dataverse elastic table. 
-ms.date: 11/13/2023
+ms.date: 11/15/2023
 author: pnghub
 ms.author: gned
 ms.reviewer: jdaly
@@ -120,16 +120,6 @@ OData-Version: 4.0
 
 `DeleteMultiple` is supported only for elastic tables. Elastic tables don't support [table relationship cascading behavior](configure-entity-relationship-cascading-behavior.md), which can result in unpredictable execution times for delete operations. If you use `DeleteMultiple` on a standard table, you get the error: `DeleteMultiple has not yet been implemented.`
 
-## Known issues
-
-The following issues will be addressed before `DeleteMultiple` becomes generally available.
-
-### DeleteMultiple plug-ins not invoked for Delete
-
-As part of the changes we made to [merge message pipelines](bulk-operations.md#message-pipelines-merged), any custom logic for the multiple version of the message must also be invoked when the single version of the message is invoked. At this time, plug-in steps registered for the `DeleteMultiple` message *are not* being called when `Delete` is used. Plug-in steps registered for `Delete` *are* being invoked when `DeleteMultiple` is used.
-
-You shouldn't migrate custom logic from `Delete` to `DeleteMultiple` until this issue is resolved. You can use `DeleteMultiple` and any logic that's associated with the `Delete` message still works.
-
 
 ## Examples
 

powerapps-docs/developer/data-platform/org-service/quick-start-org-service-console-app.md

@@ -150,7 +150,7 @@ To see and understand the `IOrganizationService` interface a little better, try
         //ServiceClient implements IOrganizationService interface
         IOrganizationService service = new ServiceClient(connectionString);
 
-        WhoAmIExample(service: serviceClient);
+        WhoAmIExample(service: service);
 
         // Pause the console so it does not close.
         Console.WriteLine("Press the <Enter> key to exit.");

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

@@ -17,7 +17,7 @@ contributors:
 
 ## Syntax
 
-`Xrm.Navigation.openAlertDialog(alertStrings,alertOptions).then(closeCallback,errorCallback);`
+`Xrm.Navigation.openAlertDialog(alertStrings,alertOptions).then(successCallback,errorCallback);`
 
 ## Parameters
 

powerapps-docs/mobile/mobile-deep-links.md

@@ -4,7 +4,7 @@ description: How to configure deep links for Power Apps mobile.
 author: trdehove
 ms.component: pa-user
 ms.topic: quickstart
-ms.date: 11/10/2023
+ms.date: 11/16/2023
 ms.subservice: mobile
 ms.author: trdehove
 ms.custom: ""
@@ -15,7 +15,8 @@ search.audienceType:
 searchScope:
   - "Power Apps"
 contributors:
-- anuitz 
+- anuitz
+- sitarampemmaraju
 ---
 
 # Use deep links with the Power Apps mobile app
@@ -24,65 +25,67 @@ Deep links let users move from one application to another on computers and mobil
 
 ## Supported deep links in the Power Apps mobile app
 
-You can open an `entityrecord` or an `entitylist` view in Power Apps mobile by using deep-link URLs from other apps. When you follow the link from an external app, the target element opens in Power Apps mobile
+You can open an `entityrecord` or an `entitylist` view in the Power Apps mobile app by using deep-link URLs from other apps. When you follow the link from an external app, the target element opens in Power Apps mobile
 
-If you're already signed in to your instance in the app, the target record is displayed when you follow the link from an external app. Otherwise, you're prompted to sign in to your instance in the mobile app; after you're signed in, the target element is displayed. You must have Power Apps mobile installed on your mobile device to use this feature.
+If you're already signed in to your instance in the app, the target record is displayed when you follow the link from an external app. Otherwise, you're prompted to sign in to your instance in the mobile app; after you're signed in, the target element is displayed. You must have the Power Apps mobile app installed on your mobile device to use this feature.
 
 ## Supported Urls parameters for a model-driven app
 
 Use the following application handler and query string parameters to compose the URL.
 
-Deep links for Power Apps mobile should start with the following:
+Deep links for the Power Apps mobile app should start with the following:
 
 ```ms-apps://<org-url>_<app-id>?tenantId=<tenant-id>&isShortcut=true&appType=AppModule&openApp=true&restartApp=true&forceOfflineDataSync=true```
 
 | **Parameter**        | **Description**                                                              |
 |----------------------|------------------------------------------------------------------------------|
 | &lt;targeted-app&gt; | <ul><li>`ms-dynamicsxrm` -> Dynamics 365 for phones</li><li> `ms-apps-fs` -> Field Service</li><li>`ms-apps` -> Power Apps</li><li>`ms-mobile-apps` -> wrapped native mobile apps</li>                                                                     |
-| &lt;org-url&gt;      | Connects to the correct org URL                                              |
-| &lt;app-id&gt;       | Opens the correct app module                                                 |
-| tenantId             | Connects to the correct tenant                                               |
-| forceOfflineDataSync | Ensures that data sync is triggered so that all the latest data is available |
+| &lt;org-url&gt;      | Connects to the correct org URL.                                              |
+| &lt;app-id&gt;       | Opens the correct app module.                                                 |
+| tenantId             | Connects to the correct tenant.                                               |
+| forceOfflineDataSync | Ensures that data sync is triggered so that all the latest data is available. |
 
 
 If opening an `entityrecord` form or creating a new `entityrecord`, use the following parameters:
 
 | **Parameter**                       | **Description**                                                                                            |
 |---------------------------------|--------------------------------------------------------------------------------------------------------|
-| etn=&lt;entity-logical-name&gt; | Designates which table to go to                                                                 |
-| pagetype=entityrecord           | Indicates that the target is a form    |
-| extraqs=&lt;form-id&gt;         | Designates which form to open for the `entityrecord`; if not specified, the default form will open. The `extraqs` parameter can also be used to default field values.        |
-| id=&lt;record-id&gt;            | Designates which specific record to go to; if left blank, the create form for the table will open |
+| etn=&lt;entity-logical-name&gt; | Designates which table to go to.                                                                 |
+| pagetype=entityrecord           | Indicates that the target is a form.    |
+| extraqs=&lt;form-id&gt;         | Designates which form to open for the `entityrecord`; if not specified, the default form opens. The `extraqs` parameter can also be used to default field values.        |
+| id=&lt;record-id&gt;            | Designates which specific record to go to; if left blank, the create form for the table opens. |
 
 If the link goes to an `entitylist` view, add the following parameters:
 
 | **Parameter**                                                | **Description**                                                     |
 |--------------------------------------------------------------|---------------------------------------------------------------------|
-| etn=&lt;entity-logical-name&gt;                              | Designates which table to go to                              |
-| pagetype=entitylist                                          | Indicates that we're going to a view                               |
-| viewid=&lt;view-id&gt;                                       | Designates which view to open                                       |
-| Viewtype= &lt;1039 if system view, 4230 if personal view&gt; | Designates whether we're going to a system view or a personal view |
+| etn=&lt;entity-logical-name&gt;                              | Designates which table to go to.                              |
+| pagetype=entitylist                                          | Indicates that we're going to a view.                               |
+| viewid=&lt;view-id&gt;                                       | Designates which view to open.                                       |
+| Viewtype= &lt;1039 if system view, 4230 if personal view&gt; | Designates whether we're going to a system view or a personal view. |
 
 ## Supported Urls parameters for a canvas app
 
 ```ms-apps:///providers/Microsoft.PowerApps/apps/<appID>?tenantId=<tenantId>&restartApp=true```
 
 | **Parameter**        | **Description**                                                                              |
 |----------------------|----------------------------------------------------------------------------------------------|
-| &lt;app-id&gt;       | Opens the correct app module                                                                 |
-| &lt;tenantId&gt;     | Connects to the correct tenant                                                               |
-| restartApp=true      | Restarts the canvas app, needed to ensure parameters are passed when the app is already open |
-  
+| &lt;app-id&gt;       | Opens the correct app module.                                                                 |
+| &lt;tenantId&gt;     | Connects to the correct tenant.                                                               |
+| restartApp=true      | Restarts the canvas app, needed to ensure parameters are passed when the app is already open. |
+| autoLoginUpn=&lt;e-mail&gt;      | Autopopulates e-mail and triggers sign-in. | 
+
   ## Supported Urls parameters for a wrapped native mobile app
 
  ```ms-mobile-apps:///providers/Microsoft.PowerApps/apps/<appID>?tenantId=<tenantId>&restartApp=true```
 
 | **Parameter**        | **Description**                                                                              |
 |----------------------|----------------------------------------------------------------------------------------------|
-| &lt;app-id&gt;       | Opens the correct app module                                                                 |
-| &lt;tenantId&gt;     | Connects to the correct tenant                                                               |
+| &lt;app-id&gt;       | Opens the correct app module.                                                                 |
+| &lt;tenantId&gt;     | Connects to the correct tenant.                                                              |
 | restartApp=true      | Restarts the canvas app to ensure parameters are passed when the app is already open. |
-  
+| autoLoginUpn=&lt;e-mail&gt;      | Autopopulates e-mail and triggers sign-in. |  
+
 ## Troubleshooting
 
 Deeplinks may open in your browser depending on the company's organizational policies and the user's device settings. Mobile Device Management (MDM) tools and device operating systems have different options and settings that impact how deeplinks are handled. If deeplinks are opening in a browser instead of directly in Power Apps mobile, make sure your MDM policies and device settings are appropriately configured.