• Replies 2 replies
  • Subscribers 338 subscribers
  • Views 105 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.

 

Parents
  • $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!

Reply
  • $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!

Children
No Data