• Replies 3 replies
  • Subscribers 336 subscribers
  • Views 33 views
  • Users 0 members are here
Related

Importing New vs. Updated Constituent Info

Shellie Sullivan
$organization

Hello everyone!

I am wondering if anyone has a solution for the following:

When importing New Constituents, you can either select Yes or No for allowing duplicates when doing an import.  Because I don't want duplicates in our system, I always select No.  However, I don't get any updated information that might be in the import.  (e.g. new phone)

I thought maybe I should choose YES instead - let the duplicates in, and then I can let the merge program find them for me and make sure I use the most up-to-date phone, etc. information when merging.  I don't know that I like this solution, however.

In a perfect world Tessitura would recognize the duplicate, like it does today, but you could choose Yes if you want to apply any new info (phone, email).  I realize this probaby wouldn't work on addresses - but it would still be helpful to have the newest phone and email data.

I'd appreciate hearing how orther organizations are dealing with this issue.

Thanks!

Parents
  • $organization

    I prefer to allow duplicates and then merge, for the reason you cite. I have found that if I disallow duplicates, some records are bumped from import that aren’t really duplicates at all.

     

    Lucie Spieler

     

    --------------------------------

    Lucie Spieler

    IT Development and Training Manager

    Editor, Season Program

    --------------------------------

    Florida Grand Opera

    8390 NW 25th Street, Miami, FL 33122

    Phone: 305-854-1643 x 1521

    Fax: 305-856-1042

    Ticket Office: 800-741-1010

    www.fgo.org

     

     

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Shellie Sullivan
    Sent: Thursday, April 15, 2010 11:45 AM
    To: Lucie Spieler
    Subject: [Tessitura Technical Forum] Importing New vs. Updated Constituent Info

     

    Hello everyone!

    I am wondering if anyone has a solution for the following:

    When importing New Constituents, you can either select Yes or No for allowing duplicates when doing an import.  Because I don't want duplicates in our system, I always select No.  However, I don't get any updated information that might be in the import.  (e.g. new phone)

    I thought maybe I should choose YES instead - let the duplicates in, and then I can let the merge program find them for me and make sure I use the most up-to-date phone, etc. information when merging.  I don't know that I like this solution, however.

    In a perfect world Tessitura would recognize the duplicate, like it does today, but you could choose Yes if you want to apply any new info (phone, email).  I realize this probaby wouldn't work on addresses - but it would still be helpful to have the newest phone and email data.

    I'd appreciate hearing how orther organizations are dealing with this issue.

    Thanks!




    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!

  • $organization in reply to Lucie Spieler

    Since most of our uploads come as a request from a specific department (i.e. Group Sales bought a list groups to call for a certain exhibit and wants them imported) we don't import dupes, but do give a list of potential dupes back to the requesting department for them to look through and manually enter or update as needed.  It's a pretty non-technical solution but it's worked so far.

Reply
  • $organization in reply to Lucie Spieler

    Since most of our uploads come as a request from a specific department (i.e. Group Sales bought a list groups to call for a certain exhibit and wants them imported) we don't import dupes, but do give a list of potential dupes back to the requesting department for them to look through and manually enter or update as needed.  It's a pretty non-technical solution but it's worked so far.

Children
No Data