Hello everyone,
Please help!
I've got a big problem here, as we have had memberships set up in Tessitura, but not really paid attention to its functionality, both in contributions and in campaign structure, and how this greatly affects what level Tessitura believes the constituent is in. We are finally really working with it for real, but have discovered that our past two years of records are a bit of a mess.
Basically the main issue that needs to be resolved for past years is that our Individual Giving campaign was a catch all for both contributions that go towards a membership, as well as other funds that are not membership applicable. So, of course this is a main reason why our records are way off. I have started a separate Membership campaign to resolve this going forward, and removed the Membership Group association from the regular Individual Giving campaign.
Ideally I would love to be able to delete the historical Membership fields in each Constituent record and then manually re-enter memberships with contribution values that only apply to memberships based on information in the constituents' contribution tabs, and then use the regular contribution-driven functionality going forward from here for future membership tracking.
Questions of course are: Is this possible? If not, what course of rectifying the situation do you recommend? Would a future run of the Membership Update Utility for this date range affect any repair work done?
Any ideas are greatly appreciated.
Thanks,
Duane
From: "Lucie Spieler" <bounce-luciespieler8144@tessituranetwork.com>To: bvarro@smm.orgSent: Thursday, November 18, 2010 7:16:50 AMSubject: RE: [Tessitura Development Forum] memberships help requested We converted a few years of membership information into Tessitura at Florida Grand Opera and ended up deleting everything that wasn’t current because there were too many issues to fix easily. Using Tessitura, fixing memberships means fixing your campaign setup so that gifts to the appropriate campaigns trigger the memberships you want, and then re-entering contributions (first deleting the incorrect memberships on the History/Memberships screen) so that they show up attached to the proper memberships. If you delete and add a membership on the History/Memberships screen without redoing the contribution, you can get the level right, but the reference to the contributions that are triggering the membership won’t be in the record, and the inception date of the membership, if it started before the current period, won’t be accurate either. When we started with Tessitura (we’re in our sixth season) I didn’t have a clue how to use SQL to fix things. I am more adventurous now; and you can do a lot with membership records on the back end to shape them up. Lucie ________________ Lucie Spieler IT Development and Training Manager Florida Grand Opera 8390 NW 25th Street Miami, FL 33122 305-854-1643 ext 1521 www.FGO.org Spam Not spam Forget previous vote This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
We converted a few years of membership information into Tessitura at Florida Grand Opera and ended up deleting everything that wasn’t current because there were too many issues to fix easily.
Using Tessitura, fixing memberships means fixing your campaign setup so that gifts to the appropriate campaigns trigger the memberships you want, and then re-entering contributions (first deleting the incorrect memberships on the History/Memberships screen) so that they show up attached to the proper memberships. If you delete and add a membership on the History/Memberships screen without redoing the contribution, you can get the level right, but the reference to the contributions that are triggering the membership won’t be in the record, and the inception date of the membership, if it started before the current period, won’t be accurate either.
When we started with Tessitura (we’re in our sixth season) I didn’t have a clue how to use SQL to fix things. I am more adventurous now; and you can do a lot with membership records on the back end to shape them up.
Lucie
________________
Lucie Spieler
IT Development and Training Manager
Florida Grand Opera
8390 NW 25th Street
Miami, FL 33122
305-854-1643 ext 1521
www.FGO.org