We have the Membership Update Utility set to run once a month with the previous month's dates set.
Very frequently (and of course without any warning until we stumble upon it) it seems like we wind up with mangled membership statuses. At least in some cases I think that this is because a membership or contribution was backdated to prior to the dates the next Utility run will examine. To fix them I then typically run the Utility manually, ideally over a small enough time period that few other records will be touched: the Membership Update Utility help page is about 90% dire warnings that manually running the report could destroy your database forever, which is disconcerting to say the least, given how often I have to do this.
So here are my questions:
1) What exactly are we worried about the Membership Utility Report mangling? It should just apply the membership rules, right? If a membership is correct it shouldn't do anything, and if it's out of date or has the wrong status or whatever, it should fix it, yes?
2) Is there any reason I shouldn't set that report to run over, say, the last year instead of the last month? As it stands the report never runs over the same period, but surely if it ran over a prior year it would generally pick up these issues where a membership or contribution has been back dated a couple of months or so.
From: "Gawain Lavers" <bounce-gawainlavers9512@tessituranetwork.com>To: bvarro@smm.orgSent: Thursday, September 12, 2013 4:21:45 PMSubject: [Tessitura Development Forum] Membership Update UtilityWe have the Membership Update Utility set to run once a month with the previous month's dates set.Very frequently (and of course without any warning until we stumble upon it) it seems like we wind up with mangled membership statuses. At least in some cases I think that this is because a membership or contribution was backdated to prior to the dates the next Utility run will examine. To fix them I then typically run the Utility manually, ideally over a small enough time period that few other records will be touched: the Membership Update Utility help page is about 90% dire warnings that manually running the report could destroy your database forever, which is disconcerting to say the least, given how often I have to do this.So here are my questions:1) What exactly are we worried about the Membership Utility Report mangling? It should just apply the membership rules, right? If a membership is correct it shouldn't do anything, and if it's out of date or has the wrong status or whatever, it should fix it, yes?2) Is there any reason I shouldn't set that report to run over, say, the last year instead of the last month? As it stands the report never runs over the same period, but surely if it ran over a prior year it would generally pick up these issues where a membership or contribution has been back dated a couple of months or so. 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! Spam Not spam Forget previous vote
Thanks Beth. That sounds like something I'd like to be able to do, even just to cover a year or so in the past that should cover any possible financial backdating likely to occur.
Just out of curiosity, I'm guessing as a Museum your memberships are pretty straightforward? Ours are geared pretty exclusively to high-level donors, and as a result the timings and benefits and payments tend to be pretty complex.