# Merge Rules

Merge Rules in DeDupeD for Dynamics 365 CRM

 The Merge Rules feature in DeDupeD for Dynamics 365 CRM enhances data deduplication with intelligent, rule-based automation. It allows administrators to define custom conditional filters for both master and subordinate records, giving organizations precise control over merge decisions.

 Using FetchXML-based custom business rules, administrators can automatically determine whether records should be merged, flagged for review, or denied, instead of relying solely on system-default logic.

 A configurable fallback merge action ensures consistent results by defining a default action (Merge, Review, or Deny) when no rules are met, preventing duplicate records from remaining unprocessed.

To configure the merge rule, [click here](/deduped/configuration/merge-settings/set-up-merge-rules.md).

 The user can select the records for merging as given below:

 

<figure><img src="/files/QKs0udgzn43OtPtg8uRd" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/EOCfB2aqioLFumFHSdcr" alt=""><figcaption></figcaption></figure>

**DeDupeD Job Runs:**

Once the job run is over, it’s result will be stored in DeDupeD Job Runs as given below:

<figure><img src="https://docs.inogic.com/~gitbook/image?url=https%3A%2F%2F272130504-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-M0QoyqUVI8_HaZ9FOSL%252Fuploads%252FADZOuF46eSCbllfyS4yj%252Fimage.png%3Falt%3Dmedia%26token%3Df02fbf64-30c1-4a30-b575-c18c013a63ea&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=431f868a&#x26;sv=2" alt=""><figcaption></figcaption></figure>

DeDupeD Job Runs Result:

The Job Results sub-grid will display:

* **Name:** name of the job run record. This usually takes the name of the master record
* **Record URL:** URL of the master record
* **Duplicate Count:** number of total subordinate records
* **Merge Count:** number of merged subordinate records
* **Review Count:** number of subordinate records to be reviewed manually
* **Deny Count:** number of subordinate records that will not be merged
* **Merge Rule Status** -> Auto-Merged, Review, Denied.
* **Merge Status** -> Merging, Merged, Partially Merged, Completed, Pending, Failed.

**Merging**- when the merging process is on going

**Merged**- when the merging process is finished and all the subordinate records are merged

**Partially merged**- when the merging process is finished and some of the subordinate records are merged, while the others may be in review/denied/ both

**Completed-** when the merging process is finished and none of the subordinate records are merged and all the subordinates are in denied

**Pending-** when the records are in review

**Failed-** when the merging process is halted mid-way and is not resumed/some error has occurred

<figure><img src="https://docs.inogic.com/~gitbook/image?url=https%3A%2F%2F272130504-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-M0QoyqUVI8_HaZ9FOSL%252Fuploads%252F6P7QMspNN2ogsTxccV7B%252F10.png%3Falt%3Dmedia%26token%3D27e7c6bc-a9fe-47bf-a123-870fcc4b8ce2&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=33f20113&#x26;sv=2" alt=""><figcaption></figcaption></figure>

Results of respective records are displayed as below:

Result showcase for each record,

* Number of records detected as duplicate records
* Number of records got merged
* Number of records under review
* Number of records got denied

<figure><img src="https://docs.inogic.com/~gitbook/image?url=https%3A%2F%2F272130504-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-M0QoyqUVI8_HaZ9FOSL%252Fuploads%252FBY5EC3y8QI0lSY89KQJO%252Fimage.png%3Falt%3Dmedia%26token%3D2863c555-b6ae-45e7-9bc3-9a2912d296e2&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=94364f51&#x26;sv=2" alt=""><figcaption></figcaption></figure>

Admin/User can find the selected master record summary in the Master Details tab as given below:

<figure><img src="https://docs.inogic.com/~gitbook/image?url=https%3A%2F%2F272130504-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-M0QoyqUVI8_HaZ9FOSL%252Fuploads%252FeeoohekYmRvX0Ro91lnK%252Fimage.png%3Falt%3Dmedia%26token%3D9b9229eb-a00c-4899-ad43-7ad01eddc9b4&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=c38c6d3c&#x26;sv=2" alt=""><figcaption></figcaption></figure>

After setting up your merge settings, you'll now have three advanced merge options to choose from: Auto Merge, Field Merge, and Address Merge—each designed to enhance the efficiency of your merging operations.


---

# 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/features/merge-rules.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.