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.
There is a parameter on the identify duplicates procedure that is intended to control when duplicates that were identified but not merged end up back on the list. The parameter is @changed_since_days. When set to NULL, a pair of potential duplicates that is not merged will not be added to the list of potential duplicates again unless one of the records has had activity since the last time the merge procedure ran. If you set it to a number, a pair of potential duplicates that is not merged will not be added to the list of potential duplicates again unless one of the records had activity in that many days.
Since this is looking at activity on an account, it's not foolproof, but it should keep most potential dupes that you don't merge off the list. I would check what the parameter is currently set for at your organization. Sometimes it gets set to several years, particularly when you first start running the procedure to find potential dupes, so that it grabs everyone. If your list of dupes is reviewed pretty regularly, you can set it to Null or a smaller time frame. Here's a link to the help topic that describes this parameter: www.tessituranetwork.com/.../Identify-Duplicates-Procedure.htm
This is super helpful Kevin, thank you! While this doesn't fix my issue directly, I see how Tess likely viewed this field as the solution to this issue. Once I can actually clear out all true dups from the list, we should be able to update this field to 7 days so we'll have a full week to review and schedule real dups and we can leave any real people to be removed from the list when it refreshes every week. Not an ideal system in my opinion but it will work. Much appreciated!