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!
Hi Shellie,
To get around this issue, we use a customized version of the Constituent Import utility that adds the new information to the record that already exists in Tessitura. I shared an older version of our custom utility a few years ago -- it's solution #184 in TASK. Tessitura's utility has been updated since I posted it, but I hope my old code might help!
~Katie Lachance-Duffy
Application Systems Analyst/Database Administrator
Theatre Alliance of Greater Philadelphia