A company I'm consulting for on the side uses Tessitura and is faced with a horrific membership structure that was setup by someone outside of any IT experience when they had initially made the conversion.
That said, one of the last things I'm determined to fix is their Membership Level acronyms. Problem is they have the exact same naming convention. Which is a huge problem in Tessitura as that is what list builder & reports use to reference when pulling membership info.
My question is, are there any other tables in SQL that need to be changed to reflect a change in membership level names, other than what's listed below?:
& also, should I look at changing views as well? (I'm not too familiar with those)
Hi Sarah,
I don't have a solid answer for you on the tables question. But you should be fine ignoring views. They are just pulling data from underlying tables. Since you are changing the data in the tables and not the field names themselves, the views should still work just fine.
- Levi
A little quick checking pointed me at a few other areas you might want to check for updates. Not an exhaustive list, but should get you started down the right path.
T_PLEDGE_BILL2, T_ORDER_CONTRIBUTION, T_ACK_RULES, T_RENEWAL_NOTICE, T_RENEWAL_NOTICE_HEADER, T_RENEWAL_SUMMARY
Several of these are empty for our orgs, but T_ACK_RULES, and T_PLEDGE_BILL2 are definitely ones you want to look into.
Hope this helps!
Wow, I wouldn't have even thought to look in those places - THANK YOU!!! You've been a tremendous help!