Sample: Detect multiple duplicate records

This sample shows how to detect and log multiple duplicate records for a specified table.

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 BulkDetectDuplicatesRequest message is intended to be used in a scenario that contains data that is needed to submit an asynchronous system job that detects and logs multiple duplicate records.

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 CreateRequiredRecords class creates some duplicate records for the sample.
3. The DuplicateRule method creates a duplicate detection rule.
4. The DuplicateRuleCondition method creates a duplicate detection rule condition for detecting duplicate records.
5. The PublishDuplicateRuleRequest method publishes the duplicate detection rule.
6. The PublishDuplicateRuleRequest returns before the publish is completed, so we keep retrieving the async job state until it is Completed

Demonstrate

The BulkDetectDuplicatesRequest method creates the BulkDetectDuplicatesRequest object

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.