I'm wondering if any other Tess organizations have done any fancy, fun integrations with Microsoft Outlook. Specifically with syncing contacts between the two.
I would like to get all of our employees actively using Tessitura as their main source for contact info for our patrons but it isn't always the fastest option. For example, if our Executive Director wants to send an email to 10 people that already live in her Outlook contacts it would be much faster for her to simply type them in the To: line of the mail rather than looking for them individually in Tess or building a list and executing an output set.
The problem we have (which may seem fairly obvious) is that our contact emails are being stored in multiple places. We may have someone reply to our Exec Dir's email requesting to update their email address. So it is updated in that specific user's Outlook contacts and no one else's Outlooks contacts. It's very possible that it also does not get updated in Tess.
I've been requested to investigate if there is a way to sync Outlook and Tess (on a nightly basis perhaps?) so that everyone always has the most up-to-date email addresses no matter which method they are choosing.
Looking forward to hearing how everyone has solved this conundrum! :)
You could look into the Exchange API (assuming you are using Exchange 2007+) if you use Outlook and want to keep it within the application.
http://msdn.microsoft.com/en-us/library/ee693007(v=exchg.80).aspx
You could have a SQL query/SP that contains the group of people want, then use the Exchange methods to create and destroy contact in the persons/shared mailbox. [simplified view on what could happen].
Few pre-requisites - Outlook, Exchange 2007 or above, the password for the user account needs storing somewhere to the program can access it to create/destroy the contacts (might prove an issue for PCI-DSS)
Personally, I wouldn't feed the changed records in Exchange back into Tessitura as you've no real way of knowing which record is newer/correct. It is possible, but you'd be creating a monster.
Unknown said: You could look into the Exchange API (assuming you are using Exchange 2007+) if you use Outlook and want to keep it within the application. [...] the password for the user account needs storing somewhere to the program can access it to create/destroy the contacts (might prove an issue for PCI-DSS) [...] Personally, I wouldn't feed the changed records in Exchange back into Tessitura as you've no real way of knowing which record is newer/correct. It is possible, but you'd be creating a monster.
You could look into the Exchange API (assuming you are using Exchange 2007+) if you use Outlook and want to keep it within the application. [...] the password for the user account needs storing somewhere to the program can access it to create/destroy the contacts (might prove an issue for PCI-DSS) [...] Personally, I wouldn't feed the changed records in Exchange back into Tessitura as you've no real way of knowing which record is newer/correct. It is possible, but you'd be creating a monster.
Very interesting that this is possible, though the issues you point out are indeed significant.