Hi all,
I'm one of the folks at our org responsible for merging dupe constituents. For ages now, there have been three constituents "stuck" in the Kept IDs column. They don't have a corresponding Delete ID, and I can't find a way to remove them from the Kept IDs column. I'm not given the option to click "UnSchedule." Does anyone know how I can get rid of these, and have a clean and tidy merge dashboard? Thanks in advance!
I had this issue some time last year... this is what I got from TASK at the time.
Here's some SQL code that should provide you with a workaround. At this point, I need to add a disclaimer that the code is not standard Tessitura code and you run this at your own risk / discretion. I would strongly suggest that you run this in your TEST environment first.
Here's the SQL code that will identify where the Kept ID is orphaned.
select * from T_POTENTIAL_DUPS where status = 'K' and customer_no not in (select keep_cust from T_POTENTIAL_DUPS where status = 'D') Once you confirm the actual number of orphaned ID's running this should clear them up. Run the Begin Tran and delete statement below. Once you confirm that the number of rows matches the same as the Select Statement you ran, you can run Commit Tran. If the numbers don't match, you run Rollback Tran. begin tran DELETE from T_POTENTIAL_DUPS where status = 'K' and customer_no not in (select keep_cust from T_POTENTIAL_DUPS where status = 'D') /* rollback tran */ /* commit tran */
We both and automated merge process and a "merge prioritization" process (which removes low importance merges), and I wind up completely purging T_POTENTIAL_DUPS monthly. It's a relatively safe thing to do. Worst case scenario, if you aren't careful you might wipe someone's scheduled merge, but you can avoid that by running an out-of-cycle merge immediately before doing the cleanup.