About Auto Merge - trillium_quality - 2.7

Trillium Quality for Dynamics Installation and Developer Guide

Product
Trillium > Trillium Quality
Version
2.7
Language
English
Portfolio
Verify
Product family
trillium_1
Product name
Trillium Quality
Title
Trillium Quality for Dynamics Installation and Developer Guide
Topic type
Overview
Administration
Reference
Installation
How Do I
Configuration
First publish date
2008

The Trillium Quality for Dynamics Auto Merge feature, available in the Standard Batch Manager, reduces the number of redundant, active contact, account, and lead records in your database. After records have been cleansed and matched, an Auto Merge request:

  • Identifies records that have a specified Pattern ID. The Pattern ID indicates the strength of the relationship of the matched records. The default Pattern ID is 100 (that is, records for which there is a very high confidence match on Name and Address) but additional Pattern IDs can be specified, as described in Pattern IDs.

  • Determines the master record based on the user’s selection of Youngest or Oldest in the request. Youngest and oldest records are determined by the record’s creation date and time.

  • Keeps the master record (youngest or oldest) active and sets the matching records to inactive.

  • When auto merging cross-matched leads into a contact records, the leads are qualified. A new contact record is created for each qualified lead and then merged into the contact record.

  • Copies data from matching records into the master (surviving) record. For example, if “emailaddress1” is a merge field and the master record’s e-mail address field is blank, an e-mail address found in a matching record will be copied into the master record. Data is only copied if the field is blank in the master record.

Note: Custom entity and customer address entity data cannot be automatically merged. They are skipped during an auto merge process.

To merge records, Trillium Quality for Dynamics uses the Microsoft Dynamics Merge process, called through the Microsoft Dynamics SDK. Child data, such as activities or orders, is merged based on the Microsoft Dynamics Merge rules and functionality.

See the Trillium Quality for Dynamics User’s Guide for information on running the Standard Batch Manager and launching an Auto Merge process.