Hello all,
We are getting ready to run the iWave integration with Tessitura for our donor research data, but we're in a bit of a holding pattern at the moment due to the integration script being developed for individual organizations and not consortia members like us.
I'm curious to hear from anybody who might use the iWave integration in their daily use of Tessitura and get a sense of the pros and cons with how it's currently set up so that we can have these thoughts in mind before the integration happens and can be prepared for any weirdness that others may have experienced.
Appreciate any thoughts on this!
Thank you,
Brian
We simply created a local table where the iwave data is imported. We have a custom screen and custom devo header where the data is displayed, list elements, and nightly jobs where the information is considered while updating PLI and suggested asks for example.
Travis
Unknown said: We simply created a local table where the iwave data is imported. We have a custom screen and custom devo header where the data is displayed, list elements, and nightly jobs where the information is considered while updating PLI and suggested asks for example. Travis
Travis,
It sounds like this isn't the "official" integration for iWave and Tessitura; is your SQL for this available to be shared or not? (Completely understand if it isn't!)
Also, are you in a consortia setting or an individual organization?
Do you all run into a similar issue as articulated by Evan with regard to credits being used on every view in your setup? If your alternative setup doesn't have that downside, we might have to consider that over the official deal.