change how Automated Duplicate Management retains Creation and Origin fields

Automated Duplicate Management currently keeps all the information from the master record, which is the record with the most recent activity or most recent creation date. This is good for address information and custom fields, but bad for tracking dates like:

Origin Source

Origin Subsource

Creation Time

Origin Application Type

Origin Referral Type

  • Guest
  • Apr 17 2015
  • Reviewed: Voting Open
LO - Current Gen / Existing Functionality
Area of the Product Database
Org/Company Name Union of Concerned Scientists
  • Attach files
  • Guest commented
    March 11, 2016 21:21

    Clients should have the ability to choose on a site-by-site basis how they want to configure the standard merge records and auto-merge. We can't turn auto-merge on because the Member ID, which is the unique key to our offline database, is overwritten in the default merge structure.

    Attachments Open full size

Related ideas