Merge branch 'main' into sitarampemmaraju-patch-1

Author: sericks007

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