Edit

Share via

Sample: Insert or update a record using Upsert

  • Article

This sample code shows how to insert or update records by using the UpsertRequest message. You can download the sample from here.

Note

This sample applies to both Dynamics 365 Customer Engagement (on-premises) and Dataverse.

How to run this sample

To obtain a local copy of all samples and build them, follow these steps:

  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 instance/organization 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 don't specify a connection string in dataverse/App.config file, a dialog opens each time you run the sample, and you'll need to enter information about which instance or org you want to connect to and which credentials you want to use. This dialog caches previous connections so that you can choose a previously used connection.

What this sample does

The UpsertRequest message is intended to be used in a scenario where it contains data that is needed to update or insert a record.

How this sample works

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

Setup

  1. Checks for the current version of the org.
  2. Import a managed solution (UpsertSample_1_0_0_0_managed.zip) that creates a sample_product entity that has an alternate key named sample_productcode. Verify that the indexes to support the alternate key are active.

Demonstrate

  1. The ProcessUpsert method processes data in the newsampleproduct.xml to represent new products and creates 13 new records.
  2. The second time when the ProcessUpsert method is called, it processes data in updatedsampleproduct.xml to represent updates to products previously created.
  3. The UpsertRequest method creates 6 updated records.

Clean up

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