Process Duplicates

Overview

• Compose the final merge output JSON for each duplicate pair.
• Decide which record is the base and which is subordinate according to row-by-row rules defined here.

How it works

• Base vs subordinate: use conditions (e.g., completeness, recency, data quality) to select the base record.
• Field-level decisions: for each field, choose the value to keep (base, subordinate, preferred, computed).
• Output JSON: rules produce a structured payload used by automatic merges (for supported connections like Dynamics/Dataverse) and webhook bodies for downstream processing.

Notes

• “Find Duplicates” defines candidate detection; “Process Duplicates” defines the values that the final merged result will contain.
• Webhook payloads allow external scripts/services to apply merges without writing bespoke merge code inside DeDuplica.