Mass Email Address - Tess ID Lookup

**Self-Hosted**

Does anyone have a way to find the corresponding customer_no's for a large number of email addresses that lives in the client? I have a way that works now, that is in an Excel spreadsheet, that queries Impresario (the user puts the email addresses on one tab and then the id's are produced when they press refresh on another), but this solution requires the user to have impresario user permissions to a specific view in impresario.

I really need a solution that can live in the client and can be accessible via "reports and utilities" so that I don't have to give the permissions at the SSMS impresario level. 

Any thoughts?

We are getting all these email addresses from people who attend zoom events and such (large numbers, like hundreds of them) and my coworkers need to know the Tess ID's to match those so they can make updates to the records (like marking an activity as attended).

Like I said, the current solution works but we don't want to keep doling out impresario permissions outside of the client, and it is increasing the workload for the few people who already have it. AND we have enough things here at SLSO that operate outside the client (Like that front of house Access form I have been asking for help with in the Dev forum). Managing yet another is not ideal.

 

Ashley Elliott

Database Administrator

St. Louis Symphony Orchestra

314-286-4198

ashleye@slso.org

Parents
  • I will also mention one more approach, which might be appropriate for you since I know you have SQL skills to employ here. 

    The Constituent Import Utility includes an empty procedure that is invoked during the import process and can hold any custom code you want to include. It's called LP_CONSTITUENT_IMPORT. You could customize this to check an imported file for any emails that already exist in the system, and populate the constituent ID if they do exist. This could be restricted to the pre-processing mode, so Tessitura doesn't generate errors about missing or invalid fields before you can do your own checking. 

Reply
  • I will also mention one more approach, which might be appropriate for you since I know you have SQL skills to employ here. 

    The Constituent Import Utility includes an empty procedure that is invoked during the import process and can hold any custom code you want to include. It's called LP_CONSTITUENT_IMPORT. You could customize this to check an imported file for any emails that already exist in the system, and populate the constituent ID if they do exist. This could be restricted to the pre-processing mode, so Tessitura doesn't generate errors about missing or invalid fields before you can do your own checking. 

Children
  • Thanks for this suggestion! It is my understanding that the order import utility picks up files from the Impftp drive on our production server. Since we don't map that drive to our staff members machines, it would be a challenge to show them how to drop the file there. When my box office coworker was using the order import utility at the beginning of this year it was a challenging experience explaining the difference between that drive and the folder that exist in the Tessitura drive that is also named Impftp (I am not actually sure why that folder exists, but it has some stuff in in from 2014 which was long before my tenure). It was also challenging showing them how to navigate to the right place using the UNC path.

    I am wondering if anyone has a solution that is user friendly in that they just save this file of email addresses on their desktop or somewhere shared and run the utility that picks up the file from that place and outputs the ID's.

    Ashley

  • Sure thing. The standard import utilities do require the file to be in a directory accessible to your SQL server. A custom solution using a report utility inside Tessitura would require this as well. The ImpFtp folder is a convenient and recommended place to do this because it usually already has the necessary permissions, but it's not strictly required. If you can set up a new shared directory that's more convenient for users and is still accessible to the SQL server, you can use that instead of ImpFtp. I know this doesn't address your desire to use the client desktop or similar but hopefully it does lower the burden a bit. Happy to see if anyone else has invented another solution.

  • Hi Ashley

    The users saves  files in the extraction Folder (or subfolder) in our environment.

    We use it for Import constituencies, NCOA  and etc.

    My understanding, this folder stays for for different Tessitura import/export process.

    Thanks, Svetlana

  • Okay... I am thinking about your suggestion here again (I always circle back to stuff on the forums- even if it is a month later). I JUST got the Constituent Import Utility to work the way it is supposed to work. Now I am going to start trying to tweak it to do this other thing. 

    I will be back with more questions soon.

    Ashley