Hello
Can any of you shed any light on the "Find Duplicates" procedure and making it more accurate at finding potential duplicate constituents.
We dont use households here. We currently have our T_defaults Id94 (Duplicate matching) parameters set on fname=2,lname=20,postal_code=3,street1=4 . We previously had fname=1 but I found that it was frequently pulling up two individuals that lived at the same address that shared the same letter of their first name so they weren't infact duplicates at all. This seems a little better with fname=2 but I wondered if any of you could add anything else that you have found has helped.
Or adjustments to the SQL procedure itself might be more what I need?
The other related issue that I have is that I dont understand how you know which constituents are new in the list each day when the list refreshes every night. We have a very long list of suggested duplicates which are not in fact duplicates, so if/when any new REAL duplicates get added, it makes it impossible to see those in the long list. Am I missing something? Our IT support has suggested that they might be able to create me a new report which extracts the information to be able to look at it in an excel document. Has anyone else set anything else up similar?
Thank you
Lianna
Hi Lianna Macari! Thank you for your post. While I don't have any personal experience with this, I'm hoping someone else in the group might jump in! Tom Brown (Past Member), I noticed you liked Lianna's post! Do you happen to have any advice/suggestions for her?
Thanks Olivia