編輯

共用方式為


Sample: Enable duplicate detection and retrieve duplicates

This sample shows how to enable duplicate detection and retrieve duplicate records.

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 IsDuplicateDetectionEnabled property is intended to be used in a scenario to enable duplicate detection rule for an organization and also for a table.

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. The Account method creates some account records to retrieve duplicates.
  3. The RetrieveDuplicateRequest method retrieves the duplicate records.
  4. The EnableDuplicateDetectionForOrg class enables duplicate detection for an organization.
  5. To enable duplicate detection set IsDuplicateDetectionEnabled = true.
  6. The RetrieveEntityRequest method retrieves the entity metadata.
  7. Set IsDuplicateDetectionEnabled = true to update the duplicate detection flag.
  8. The UpdateEntityRequest updates the entity with duplicate detection set to true.

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.