In going through the Merge Duplicate process, there are some constituents that were auto identified as potential duplicates but we have determined to not be duplicates. Does anyone know a way of individually removing these constituents from the potential dups window at the top of the merge screen? I'm currently left with a bunch of constituents that were identified as potential dups but are not and have to sift through them all every time I go to schedule merges.
Gawain Lavers is correct. Interestingly, though, there IS a custom parameter set up for the duplicate identification process. But it is set to nothing. I think maybe there is intended to be another local procedure for custom identification? Or maybe there was the idea there at some point and it got shelved? At any rate, in our database at least, in the procedure that identifies potential merges (AP_IDENTIFY_DUPLICATES) there DOES exist an entry variable called @identify_method_custom which is set to -1, which matches the ID on the table TR_DUPLICATE_IDENTIFY_METHOD which then says "Custom Potential" that was created back in 2012.
But I have neither heard nor seen anything of that since then. So maybe that died a quiet death.
John A. Moskal II
There's no built in (e.g. LP_IDENTIFY_DUPLICATES) plan for adding your own entries to the Potential Duplicates list, but I use that method id for my custom systems for adding Potential Ids (and auto-scheduling merges). It happens to have key relevance to how household affiliates are processed (yes, that took me days of digging through the code).