Sample: Execute multiple requests

  • Artikel

This sample shows how to execute multiple organization message requests by using a single web service method call, passing ExecuteMultipleRequest as a parameter. Reducing the number of message requests that must be transmitted over the network results in increased message processing performance.

SDK for .NET: Execute multiple requests sample code

How to run this sample

  1. Download or clone the Samples repo so that you have a local copy.
  2. (Optional) Edit the dataverse/App.config file to define a connection string specifying the Microsoft Dataverse instance you want to connect to.
  3. Open the sample solution in Visual Studio and press F5 to run the sample. After you specify a connection string in dataverse/App.config, any sample you run will use that connection information.

If you do not specify a connection string in dataverse/App.config file, a dialog will open each time you run the sample and you will need to enter information about which Dataverse instance you want to connect to and which credentials you want to use. This dialog will cache previous connections so that you can choose a previously used connection.

Those samples in this repo that require a connection to a Dataverse instance to run will include a linked reference to the dataverse/App.config file.

What this sample does

The ExecuteMultipleRequest message is intended to be used in a scenario where it contains data that is needed to execute one or more messages requests as a single batch operation, and optionally return a collection of results.

How this sample works

In order to simulate the scenario described in What this sample does, the sample will do the following:

Setup

Checks for the current version of the org.

Demonstrate

  1. The ExecuteMultipleRequest method creates the ExecuteMultipleRequest object.
  2. The ExecutingMultipleSettings method assigns settings that define execution behavior: continue on error, return responses.
  3. The OrganizationRequestCollection method creates an empty organization request collection.
  4. The CreateRequest method is added for each table to the request collection.
  5. The GetCollectionOdEntitiesToUpdate class updates the tables that are previously created.

Clean up

Display an option to delete the records created in the Setup. The deletion is optional in case you want to examine the tables and data created by the sample. You can manually delete the records to achieve the same result.