• Replies 2 replies
  • Subscribers 338 subscribers
  • Views 106 views
  • Users 0 members are here
Related

Mass Membership Changes

Matt Gonzales
$organization

 

Per our Development Coordinator:

Our Annual Fund team has decided to set our “Lapse-  x  months after expiration” to “0” in the membership rules. After I change this rule, those who are currently marked as Lapsed should have an Active status instead. I tested this in our TEST database:

  • Changed the membership rule to “0”
  • Adjusted the expiration date of a constituent with Lapsed status forward a year
  • Ran the Membership Update Utility report
  • Every other Lapsed membership changed to Inactive; the one I adjusted forward remained Lapsed

So, having tested unsuccessfully, can we mass change them all (on the back end in SQL) to Active, as well as increase the membership expiration date forward?  What are the implications to the rest of Tessitura?

Your advice would be most appreciated, Tessiturians.

BONUS TRIVIA MORSEL:  The British send more Valentine's Day cards than any other country.

 

  • $organization
    Hi Matt,

    We have our lapse set to 0 as well - we need it that way, as museum members frequently wait to renew based on exhibit or film schedules, and they'd have fits if they didn't get a full year of membership from their purchase date.  It's generally been fine, but we have had some issues with the Inception date and NRR status fields.   Our understanding from the standard documentation was that the "reinstate" field determined whether a membership kept its inception date and whether it was marked as New, Renew or Reinstate - if they rejoined before they hit the end of the Reinstate period, they would keep their original inception date and be marked as a reinstate.  But our data wasn't acting that way.  We discovered a couple possible reasons:

    - Tessitura's response to our ticket about this issue was that "what you are seeing is expected behavior if your LAPSE date is not set. You will need to populate that field with a valid number (not 0 nor NULL) in order for the inception date to remain unchanged between the expiration and the reinstate periods."  So it seems that the standard documentation is assuming that you have a Lapse period of at least 1 month.

    - We also found that gifts processed in the Contributions Module seemed to follow the rules, but gifts processed from Orders did not.  This will hit you if you take gifts via frontline staff or the web.  My understanding from our ticket is that this is fixed in v.10 and you can also use the procedure in v. 9.  But we haven't tried it ourselves yet.

    Sorry I can't offer you final resolution on this yet, in terms of whether the problem is caused by the Lapse period, the orders v contributions bug, or both...but I'd recommend investigating this before you move forward, as lacking good Inception Date and NRR status data can really make your life harder when you try to analyze your base.  Let me know if you want more detail.

    Beth


    * * * * *
    Experience a once-in-a-lifetime opportunity: see authentic 2,000-year-old manuscripts, including the earliest biblical writings. The Dead Sea Scrolls. Once forgotten. Now unforgettable. Visit www.smm.org/scrolls.

    Elizabeth A Varro
    Membership Manager
    Science Museum of Minnesota
    (651) 265-9829

    From: "Matt Gonzales" <bounce-mattgonzales9808@tessituranetwork.com>
    To: bvarro@smm.org
    Sent: Monday, August 30, 2010 5:57:30 PM
    Subject: [Tessitura Technical Forum] Mass Membership Changes

     

    Per our Development Coordinator:

    Our Annual Fund team has decided to set our “Lapse-  x  months after expiration” to “0” in the membership rules. After I change this rule, those who are currently marked as Lapsed should have an Active status instead. I tested this in our TEST database:

    • Changed the membership rule to “0”
    • Adjusted the expiration date of a constituent with Lapsed status forward a year
    • Ran the Membership Update Utility report
    • Every other Lapsed membership changed to Inactive; the one I adjusted forward remained Lapsed

    So, having tested unsuccessfully, can we mass change them all (on the back end in SQL) to Active, as well as increase the membership expiration date forward?  What are the implications to the rest of Tessitura?

    Your advice would be most appreciated, Tessiturians.

    BONUS TRIVIA MORSEL:  The British send more Valentine's Day cards than any other country.

     



    --
    View this message online at http://www.tessituranetwork.com/COMMUNITY/forums/p/3221/10695.aspx#10695 or reply to this message
    --
    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical 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!

  • $organization

    Hi Matt,

    Just looked over the AP_MEMBERSHIP_UPDATE report, and I see no logic within it to ever change a current status of lapsed back into active.

    I think updating the current status and expiration date in SQL should be fine, but I would always recommend opening a TASK ticket for such things, just to be sure.

    Cheers!