Stronger duplicate criteria when importing constituents

While the current duplicate engine is very powerful, I am suggesting that the duplicate tool look to linked records.  Husband has an Individual account.  Has a Spouse record (where she does not have her own record).  If the wife attends an event (or any other source of data resulting in an import), we would like the validation report to reject the import and list her as a possible duplicate for manual processing.  As it stands, the spouse record is added, and now we have non-linked records at the same address.  Feels like the system could solve that one for us...

 

Additionally, can the dupe engine on import give us options of what we would (or would not) like to be treated as a duplicate?  First/Last/Middle? Address only, Zip plus4? Spouse, nickname, address/last name?

  • Micah Story
  • Apr 10 2018
  • Attach files