Skip to content

Commit 34c2638

Browse files
authored
Merge pull request MicrosoftDocs#1663 from MarkMpn/patch-7
Add reference to async Merge requests
2 parents 84addf6 + a8d6bf2 commit 34c2638

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

powerapps-docs/developer/common-data-service/org-service/use-executeAsync.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,14 +17,16 @@ search.app:
1717
---
1818
# Use ExecuteAsync to execute messages asynchronously
1919

20-
Except for two, all data operations using the SDK assembly request classes are synchronous.
20+
Except for three, all data operations using the SDK assembly request classes are synchronous.
2121

2222
Importing a solution is one operation which can require considerable resources, so there is an option to execute this operation asynchronously using the <xref:Microsoft.Xrm.Sdk.Messages.ExecuteAsyncRequest> request class. The <xref:Microsoft.Crm.Sdk.Messages.DeleteAndPromoteRequest> request class performs similar resource intensive operations.
2323

2424
Importing a solution asynchronously improves system performance by postponing message execution until some later time when the server load may be less. Interactive users do not have to wait for the target message to execute before they can continue. This is especially useful when importing solutions which may take a few minutes or more to execute.
25+
26+
Merging records with a large number of related activities or other entity types can also take a long time to update all the related records, so executing these in the background can improve the user experience.
2527

2628
> [!NOTE]
27-
> <xref:Microsoft.Crm.Sdk.Messages.ImportSolutionRequest> and <xref:Microsoft.Crm.Sdk.Messages.DeleteAndPromoteRequest> are the only request classes that can be used with the `ExecuteAsync` message.
29+
> <xref:Microsoft.Crm.Sdk.Messages.ImportSolutionRequest>, <xref:Microsoft.Crm.Sdk.Messages.DeleteAndPromoteRequest>, and <xref:Microsoft.Crm.Sdk.Messages.MergeRequest> are the only request classes that can be used with <xref:Microsoft.Xrm.Sdk.Messages.ExecuteAsyncRequest>.
2830
2931
Use the <xref:Microsoft.Xrm.Sdk.Messages.ExecuteAsyncRequest> request class to execute a message asynchronously. You configure the request and pass the request instance as an argument to <xref:Microsoft.Xrm.Sdk.IOrganizationService>.<xref:Microsoft.Xrm.Sdk.IOrganizationService.Execute*>. <xref:Microsoft.Xrm.Sdk.Messages.ExecuteAsyncResponse> returns with the ID of the asynchronous job. You can (optionally) query the job using the ID to find out its current state.
3032

@@ -64,4 +66,4 @@ You can then poll the [AsyncOperation](../reference/entities/asyncoperation.md)
6466
[Execute multiple requests using the Organization service](execute-multiple-requests.md)
6567

6668

67-
69+

0 commit comments

Comments
 (0)