Hello - We've been using P2 for about a year now, and just were informed we have been handing email changes improperly. In order for the email change to be recognized in P2 it has to be changed in the P2 Custom Tab, not the Contact Details Tab. We have restricted many of our Tessitura users including Front Desk employees from accessing the P2 Custom Tab as you can change people's subscription preferences and mess up their accounts easily from that tab. However, it now looks like we'll have to give everyone access at all levels. Has anyone else in a large organization had to handle this? How did you manage access?Thanks!Jane EsterquestIsabella Stewart Gardner Museum
We are thinking of moving from WordFly to P2, and given we are in a consortium environment where some organizations are on P2 and others aren't, I find this a bit worrying. What sorts of email changes are we talking about that don't sync with Tessitura?
We've been with Prospect2 for a little over a year and, so far, I haven't found anything Tessitura-wise that we can't do with P2. As a matter of fact, given that P2's main focus is Tess interaction, we're able to do more than we could with WordFly. What are your main concerns?
My concern is as Jane Esterquest suggests, changes made in Tessitura don't propagate to P2, but only the reverse. In our environment, changes happen in Tessitura all the time, so that's why I'm interested in which changes only sync one-way.
I guess it depends on how you're managing patron accounts. We generally pull fresh lists, which then updates patron information in P2. WordFly also doesn't send information back to Tess. It's what saved us all when WordFly was hacked.
Wordfly gave us a sample job to sync WordFly unsubscribes back to Tess (back before contact points and preferences, when we just used an attribute), and we wrote some custom code to sync Interests and, for a time, WordFly Pages used as surveys. I guess we might be able to do the same sort of customizations with P2. We push fresh lists from Tessitura to WordFly, but I noticed at other orgs in our consortium, the P2 users and the Tessitura users are often not the same users. I'll definitely look closely at interactivity before we take the P2 plunge.