Duplicate Constituent Management Tool in 7.92 - is it a Knowledgebase ghost?

Jana Byington-Smith

There is no Knowledgebase 'how to' documentation on the Duplicate Constituent Management Tool in 7.92, at least as far as I can tell after a LOT of time looking. There is one algorithm description and three problem options, but no 'how to'. Any ideas about where they've hidden the sucker?

JoAnn Strommen

Jana Byington-Smith:
There is no Knowledgebase 'how to' documentation on the Duplicate Constituent Management Tool in 7.92, at least as far as I can tell after a LOT of time looking. There is one algorithm description and three problem options, but no 'how to'. Any ideas about where they've hidden the sucker?

Per KB BB51429 if you're using 7.92 we really don't have any options to set the search criteria like there was in previous versions.  I believe there's a suggestion on this in the User Voice/Discover suggestions.  Doesn't seem to work the best for us at finding dups.

From BB51429: 

In The Raiser's Edge 7.92 and above:
Starting in RE 7.92, there is a Blackbaud defined algorithm which will weight and intelligently surface the best, most logical results based on the search criteria entered. The algorithm considers the following data fields: name, middle initial, suffix, address, phone number and email. This algorithm is hard-coded and is used by default within the database. The duplicate fields listed above are no longer present in version 7.92.

Note: For more information on managing duplicate records in version 7.92, see How to find and prevent duplicate records.

Jana Byington-Smith

JoAnn Strommen:

Per KB BB51429 if you're using 7.92 we really don't have any options to set the search criteria like there was in previous versions.  I believe there's a suggestion on this in the User Voice/Discover suggestions.  Doesn't seem to work the best for us at finding dups.

From BB51429: 

In The Raiser's Edge 7.92 and above:
Starting in RE 7.92, there is a Blackbaud defined algorithm which will weight and intelligently surface the best, most logical results based on the search criteria entered. The algorithm considers the following data fields: name, middle initial, suffix, address, phone number and email. This algorithm is hard-coded and is used by default within the database. The duplicate fields listed above are no longer present in version 7.92.

Note: For more information on managing duplicate records in version 7.92, see How to find and prevent duplicate records.

Thanks, JoAnn. The algorithm is not ideal. We have some doozy duplicates that make no sense in reality. My problem is about using the plug-in utility tool in 7.92, not the Admin duplication report. All support in Knowledgebase for the utility is for 7.93. We won't upgrade until fall (on our own servers, packaged environments), so we have to make the utility function in 7.92 with the query we generate in Admin. I think this is probably a custom solutions issue now.