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 not a clean way of doing this in Tessitura. I've created an Association ("Not a Duplicate") to connect two accounts that are confirmed not duplicates, but you then have to have some kind of system to strip those matches from your Potential Duplicates list.
Late to the party here but we're addressing this topic in real time. Association is a great idea, but we went with a simple attribute with the reciprocal patron id. I created an independent procedure that looks at T_POTENTIAL_DUPS and IDs anyone with the attribute and the value is the reciprocal ID on the table they get stripped from the table. We're very early in setup and testing but the idea is that we'd schedule it to run after the identifying procedure so that we can turn it off if needed. Something like
CREATE TABLE #Results (ID INT,P_DUPE INT);INSERT INTO #Results (ID, P_DUPE) /*creating a temp table that matches customer IDs with potential dupes*/select distinct d1.customer_no, d2.customer_no as p_dup from T_POTENTIAL_DUPS d1join t_potential_dups as d2 on d2.criterion = d1.criterionwhere d1.customer_no <> d2.customer_no
delete from T_POTENTIAL_DUPSwhere customer_no in(select a.id from #results ajoin tx_cust_keyword b on b.customer_no = a.idwhere b.keyword_no = 798 /*The False dupe keyword ID*/and b.key_value = a.p_dupe)