Hi all,
I'm new to an organisation where it seems a lot of duplicate records were created during the V11 upgrade, mostly teachers affiliated to school records, i.e. EXACT matching records.
Strangely, they aren't being picked up as potential duplicates in the constituent merge utility. The values in Duplicate Matching in T_DEFAULTS are: fname=1,lname=20,postal_code=3,street1=10.
Creating an auto-merge script is definitely on the horizon but if anyone is privy to this issue, I'd love to hear from you, thanks!
Good day, Kevin
We, too, experience the same problem.
We finally flipped the Tessitura switch on, recently importing all constituent data from our legacy ticketing system.
I wrote many custom SQL queries to search for potential duplicates (and I always find many), but it is often a manual effort.
Our Duplicate Matching values are: fname=3, lname=3, postal_code=4, street1=3
However, I often find potential duplicates with the SQL code that are not picked up by the AP_IDENTIFY_DUPLICATES stored procedure.
I’ll try your Duplicate Matching values. If you find better values, please share.
And, if I can help, please contact me directly.
Regards
Wendell Baskin
Bass Hall – Fort Worth
wbaskin@basshall.com
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Kevin Madeira Sent: Thursday, July 25, 2013 20:36 To: Wendell Baskin Subject: [Tessitura Technical Forum] Potential duplicate records
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!