Welcome to Luminate Ideas!

Please submit all product enhancement ideas below. We welcome your feedback; your ideas will be reviewed by the Product Manager that oversees the development of that part of the product on an ongoing basis and updated with its current status monthly based on our product planning process. Ideas you submit could help us shape features currently in development or grow our repository of requirements for our next big enhancement. Thank you for taking the time to share your thoughts and expertise with us.

If you believe you are experiencing a defect please contact Support.

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
Area of the Product Database
Org/Company Name Union of Concerned Scientists
  • Attach files
  • Matt Lindsay commented
    11 Mar, 2016 09:21pm

    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.

Privacy Policy | Safe Harbor Notice | Terms of Use | Acceptable Use Policy | © 2019 Blackbaud, Inc. All Rights Reserved