# Set Up Duplicate Detection Using Related Entity Fields in Dynamics CRM

{% hint style="info" %}
**Note:** To use the Related Entity Duplicate Detection feature, please delete any existing configurations that contain fuzzy matching conditions and create a new configuration. This ensures that the application functions smoothly and that the related entity duplicate detection rules work as expected.
{% endhint %}

**Detecting Hidden Duplicate Contacts Using Related Account Information**

Data duplication in Dynamics 365 CRM doesn’t always occur within a single entity; sometimes it exists across related entities, making it harder to detect with standard duplicate rules.

For example, a sales team may create multiple Contact records that appear different but actually belong to the same person, even though the company name linked to them may be slightly different.

**Example**

A salesperson creates a new contact:

* **Contact Name:** Michael Johnson
* **Email:** <michael.johnson@techvision.com>
* **Account:** TechVision Ltd.

However, a similar contact already exists in CRM:

* **Contact Name:** Mike Johnson
* **Email**: <michael.johnson@techvision.com>
* **Account:** TechVision Limited

Although the contact names are slightly different and the company names are written differently, both records share the same email address, which strongly indicates that they belong to the same individual.

Standard duplicate detection might miss this situation because it usually checks only the fields within the Contact entity and may not consider the relationship with the Account (Company).

With DeDupeD – Related Entity Duplicate Detection, the system can evaluate Contact fields (like Email) along with fields from the related Account entity (such as Company Name). This helps the system detect potential duplicates even when the company names are written differently, allowing users to review and merge the records with confidence, keeping CRM data clean and accurate.

## Step-by-Step Process to Configure Related Entity Duplicate Matching:

### &#x20;Step 1: Create a Duplicate Matching Rule

* &#x20;Navigate to DeDupeD → Entity Configuration
* Select your entity (e.g., Contact)
* Go to Duplicate Matching Rules
* Click + New Duplicate Matching Rule
* Provide a meaningful name\
  Example: Contact\_Related\_Account\_Name

### &#x20;Step 2: Configure Rule Settings

* Primary Entity → Contact
* Matching Entity → Contact
* Enable Exclude Inactive = Yes (recommended)

This ensures only active, relevant records are evaluated

<figure><img src="https://272130504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M0QoyqUVI8_HaZ9FOSL%2Fuploads%2Fmpk28FURZSzqJGvjv9m5%2FRE_Config_1.png?alt=media&#x26;token=3869004b-caf2-492f-b8e3-51d7841c6009" alt="Related Entity Data Deduplication in Dynamics 365 - Configuration"><figcaption></figcaption></figure>

### Step 3: Add Related Entity Field

* Click New Duplicate Matching Condition
* In Primary Entity Field → Select an attribute
* Switch to Related tab
* Expand: Company Name (Account)
* Select: Account Name

This is the breakthrough: You are now matching records based on a lookup’s related field, not just the contact itself.

<figure><img src="https://272130504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M0QoyqUVI8_HaZ9FOSL%2Fuploads%2FkKsXjla4jH3BkjFQ5P6G%2FRE_Config_2.png?alt=media&#x26;token=089b2088-b81e-4e41-9e92-e02d0f41944a" alt="Related Entity Data Deduplication in Dynamics 365  - Configuration "><figcaption></figcaption></figure>

<figure><img src="https://272130504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M0QoyqUVI8_HaZ9FOSL%2Fuploads%2FDiMjWVnxHYafweNuGcbK%2FRE_Config_3.png?alt=media&#x26;token=43117638-de5b-4154-ace6-e60387cca4a4" alt="Related Entity Data Deduplication in Dynamics 365 - Configuration"><figcaption></figcaption></figure>

### Step 4: Map Matching Entity Field

Repeat the same selection:

* Matching Entity Field → Account Name (from related Account)

This ensures both sides of comparison use the same logic.

<figure><img src="https://272130504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M0QoyqUVI8_HaZ9FOSL%2Fuploads%2FmcqLyF6i1KwKzcFJIrj7%2FRE_Config_4.png?alt=media&#x26;token=c82a11ff-00a6-4297-9472-4c754ae234ad" alt="Related Entity Data Deduplication in Dynamics 365 - Configuration"><figcaption></figcaption></figure>

<figure><img src="https://272130504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M0QoyqUVI8_HaZ9FOSL%2Fuploads%2F0f7rnR1ZB1ELyjPQTNGv%2FRE_Config_5.png?alt=media&#x26;token=ab90f2e6-3685-49a5-ad5e-0084502451de" alt=""><figcaption></figcaption></figure>

### Step 5: Choose Matching Criteria

You can choose any duplicate matching criteria according to your business needs. For example, Set:

* Matching Criteria → Fuzzy
* Accuracy Level → High
* Ignore Blank Values → Yes

**Why Fuzzy?**

* Handles variations like:
* “ABC Pvt Ltd” vs “ABC Private Limited”
* “Brian Robinson” vs “B. Robinson”

<figure><img src="https://272130504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M0QoyqUVI8_HaZ9FOSL%2Fuploads%2F71Cl1DhiiQYkib31KveP%2FRE_Config_6.png?alt=media&#x26;token=33511b83-980a-4264-a91c-3a91a87d76b1" alt="Related Entity Data Deduplication using Fuzzy Matching in Dynamics 365"><figcaption></figcaption></figure>

<figure><img src="https://272130504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M0QoyqUVI8_HaZ9FOSL%2Fuploads%2FDi9Y8dIvIrtmyUR6ilPo%2FRE_Config_7.png?alt=media&#x26;token=964bcd71-dc12-458a-8ab7-66d8114c7744" alt="Related Entity Data Deduplication using Fuzzy Matching in Dynamics 365"><figcaption></figcaption></figure>

### Step 6: Save & Publish Rule

Click Save and Close

* Click Publish

Your rule is now active and ready for detection.

<figure><img src="https://272130504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M0QoyqUVI8_HaZ9FOSL%2Fuploads%2F4EJLaRiwJsRG935AOiGl%2FRE_config_8.png?alt=media&#x26;token=50889146-b0ef-4885-8d2d-5c21c13ff563" alt="Related Entity Data Deduplication in Dynamics 365 CRM - Configuration"><figcaption></figcaption></figure>

### Step 7: Verify Published Rule

* Navigate back to Entity Configuration
* Confirm:
* Rule appears under Published Rules
* Status = Published

<figure><img src="https://272130504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M0QoyqUVI8_HaZ9FOSL%2Fuploads%2Fv5RbGKBVCdPauAllbU5h%2FRE_Config_9.png?alt=media&#x26;token=b45b9ac2-abee-4cbd-a6a3-c75b91c6b977" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
For further queries, reach out to us at <crm@inogic.com>
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.inogic.com/deduped/configuration/set-up-duplicate-detection-using-related-entity-fields-in-dynamics-crm.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.