> For the complete documentation index, see [llms.txt](https://docs.inogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inogic.com/deduped/features/merge-rules.md).
# 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:
**DeDupeD Job Runs:**
Once the job run is over, it’s result will be stored in DeDupeD Job Runs as given below:
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
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
Admin/User can find the selected master record summary in the Master Details tab as given below:
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.
### Merge Rules Support for UI-Based Merge Operations
When you merge duplicate records manually from the Merge UI, DeDupeD now checks those records against your configured Merge Rules before the merge happens — the same validation that already applied to scheduled, bulk, and auto-merge jobs.
Here's how it works: when you open the Merge UI, DeDupeD first evaluates the selected master record against your configured master deciding rules, and then evaluates the subordinate records against your configured Merge Rules. Each subordinate is placed into one of three states — Merge, Review, or Deny — and the Merge UI shows you these results before you complete the merge, so you always know which records will actually be merged.
If you change the master record in the Merge UI before completing the merge, DeDupeD re-evaluates the Merge Rules against the newly selected master, and the statuses update accordingly.
Let's walk through what this looks like in practice.
#### Step 1: Open the Merge UI
From any duplicate-detected view, select a record and click Show Duplicates to open the Merge UI. This lists the current record's duplicates.
Select the duplicate records you want to merge and click **Merge**.
#### Step 2: DeDupeD Evaluates the Master and the Duplicates
Once the Merge UI opens, DeDupeD evaluates the selected master record against your master deciding rules, and each subordinate record against your Merge Rules. Every record is then labeled with one of the following statuses:
| Status | What it means |
| ------ | ------------------------------------------------------------------------ |
| Merge | The record is eligible and will be included in the merge. |
| Review | The record needs manual review and will not be merged in this operation. |
| Deny | The record is not eligible and cannot be merged. |
#### Step 3: Check the Status of Each Record
Each record's status is shown right on its card. In this example, one subordinate is eligible for merge, one is marked for Review, and one is Denied — you can see the reason ("Subordinate disabled by merge rule") directly on the disabled records.
#### Step 4: Complete the Merge
The Finish button reflects what's actually mergeable:
* Finish is disabled if the master itself is Review or Deny, or if every subordinate is Review/Deny (leaving nothing eligible to merge).
* Finish stays enabled as long as the master is eligible (Merge) and at least one subordinate is eligible for merge — so you can proceed even if some duplicates are held back for review or denied.
Click Finish to complete the merge of the eligible record(s).
#### Step 5: View the Job Run Results
After the merge completes, open the DeDupeD Job Runs entity to see the outcome. The job run shows how many records were merged, how many need review, and how many were denied — here, 3 merged and 1 held for review.
#### Step 6: Review the Records Marked for Review
Open the job run and click Show Duplicates to see the records still awaiting action. Records under review can be selected and merged from here once you've confirmed they're eligible — select the duplicate group and click Merge.
Note: the master record cannot be changed from Job Run Results — master selection only happens in the Merge UI, before a merge is completed.
#### Step 7: Merge the Now-Eligible Review Record
This reopens the same Merge UI preview, showing the current Merge/Review/Deny status for the record and its master. If it's now eligible, click Finish to complete the merge.
#### Step 8: View the Updated Merge Count
Back in DeDupeD Job Runs, the record now reflects the updated result — the previously-reviewed record has been merged, bringing the total merged count up and the review count down to zero.
