Hello, I'm currently running some duplicate merges and there are some constituents that Tessitura thinks are duplicates but they are not. Is there any way to remove those people from the list of duplicates? I haven't scheduled any of them because I would like to keep both profiles. I also read that you can go and edit the way duplicates are matched but 90% of the time it's accurate. Is there an "easy" way to fix this? Thank you!-Jane EsterquestCelebrity Series of Boston Marketing Assistant
Hi Jane
There's no easy way, as far as I'm aware. You can give the constituents the "Void Merge" attribute, but that will block them from being merged with any other record, not just the mismatched pair.
\Our approach to this issue (eventually) was to create an Association Type called "Do Not Merge", and add an association of that type between pairs of constituents identified as not dupes.
... but then to activate that, you need to do some SQL customisation of at least the Identify Dupes stored procedure, which populates the list in the merge screen, so that it will exclude any pairs of constituenti with that association.
It would also be advisable to customise the Merge Validation proc, so that it will decline to schedule merges of those pairs, if someone attempts to schedule them manually, and as the final step, customise the merge routine itself to abort the merge if they are somehow scheduled. Three lines of defense - like the Maginot Line but hopefully more effective.
None of that is terribly difficult if you have the sql skills - and it's all stuff that Tess specifically makes available for customisation, so you're not doing anything you shouldn't - but it's not in the Easy category,and certainly not possible without access to reasonable SQL coding skills.
Ken