• Replies 8 replies
  • Subscribers 340 subscribers
  • Views 137 views
  • Users 0 members are here
Related

Identify Duplicates in Constituent Import

Frances O'Connell
$organization

Hi everybody,

I have been doing a lot of constituent imports lately and am having a lot of trouble with the Identify Duplicates part of the Utility.  In essence, it doesn’t seem to be catching all of our duplicates.  I checked the Duplicate Matching settings in our T_DEFAULTS table and they seem to be sufficient, but regardless, it is not identifying duplicates even when they match these parameters – when the import name and address information is really, exactly the same as what exist in the db.  For reference, our duplicate matching settings are as follows:

fname=1,lname=20,postal_code=3,street1=3

Has anyone seen this happen before?  To note, we are still on v.10. 

Thanks!

Frannie

Parents
  • $organization

    You’ve indeed spotted a few issues with this function.  I’ve followed up with Dave in the support ticket that was opened.  We’ll be posting a v11+ hotfix on TASK for this once we’ve completed internal testing.  This is also fixed for v12.

     

    +Ryan Creps

    +Tessitura Network

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of David Frederick
    Sent: Monday, May 6, 2013 3:46 PM
    To: Ryan Creps
    Subject: Re: [Tessitura Technical Forum] Identify Duplicates in Constituent Import

     

    Hi Frannie,

    I'm working on using Constituent Import to load in some schools and found this thread while troubleshooting duplicate resolution. Essentially, it's not finding any duplicates.

    I audited the procedure and found at least two bugs in the FT_DUPLICATES_FOR_NEW_CONSTITUENT that is causing the problem. One relates to reading our duplicate check values from T_DEFAULTS and the other relates to it skipping rows, like organizations and households, that have a NULL fname. I'm opening a TASK ticket to get this resolved and in the meantime, implementing some corrections myself so we can get this working properly. 

    Are the records you are having trouble with organizations, individuals, or a combination of the two? 

    Thanks,
    David 

    From: Frances O'Connell <bounce-francesoconnell5073@tessituranetwork.com>
    Sent: 4/4/2013 10:06:52 AM

    Hi everybody,

    I have been doing a lot of constituent imports lately and am having a lot of trouble with the Identify Duplicates part of the Utility.  In essence, it doesn’t seem to be catching all of our duplicates.  I checked the Duplicate Matching settings in our T_DEFAULTS table and they seem to be sufficient, but regardless, it is not identifying duplicates even when they match these parameters – when the import name and address information is really, exactly the same as what exist in the db.  For reference, our duplicate matching settings are as follows:

    fname=1,lname=20,postal_code=3,street1=3

    Has anyone seen this happen before?  To note, we are still on v.10. 

    Thanks!

    Frannie




    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!

Reply
  • $organization

    You’ve indeed spotted a few issues with this function.  I’ve followed up with Dave in the support ticket that was opened.  We’ll be posting a v11+ hotfix on TASK for this once we’ve completed internal testing.  This is also fixed for v12.

     

    +Ryan Creps

    +Tessitura Network

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of David Frederick
    Sent: Monday, May 6, 2013 3:46 PM
    To: Ryan Creps
    Subject: Re: [Tessitura Technical Forum] Identify Duplicates in Constituent Import

     

    Hi Frannie,

    I'm working on using Constituent Import to load in some schools and found this thread while troubleshooting duplicate resolution. Essentially, it's not finding any duplicates.

    I audited the procedure and found at least two bugs in the FT_DUPLICATES_FOR_NEW_CONSTITUENT that is causing the problem. One relates to reading our duplicate check values from T_DEFAULTS and the other relates to it skipping rows, like organizations and households, that have a NULL fname. I'm opening a TASK ticket to get this resolved and in the meantime, implementing some corrections myself so we can get this working properly. 

    Are the records you are having trouble with organizations, individuals, or a combination of the two? 

    Thanks,
    David 

    From: Frances O'Connell <bounce-francesoconnell5073@tessituranetwork.com>
    Sent: 4/4/2013 10:06:52 AM

    Hi everybody,

    I have been doing a lot of constituent imports lately and am having a lot of trouble with the Identify Duplicates part of the Utility.  In essence, it doesn’t seem to be catching all of our duplicates.  I checked the Duplicate Matching settings in our T_DEFAULTS table and they seem to be sufficient, but regardless, it is not identifying duplicates even when they match these parameters – when the import name and address information is really, exactly the same as what exist in the db.  For reference, our duplicate matching settings are as follows:

    fname=1,lname=20,postal_code=3,street1=3

    Has anyone seen this happen before?  To note, we are still on v.10. 

    Thanks!

    Frannie




    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!

Children
No Data