One of our Development Associates was transferring memberships from our old membership program to our new program and accidentally deactivated the wrong membership on one of our high end donors. It didn't get caught until today (several weeks after it happened). Can I fix this quickly from the back end or should they manually recreate the membership? (I thought there was an answer to this somewhere, but I couldn't find it on Task or in the Forums).
Thanks in advance.
-steve carlock
Santa Barbara Center for the Performing Arts
Thanks Lucie. It worked perfectly.
-steve
Information Technology Manager
The Granada
(805) 899-3000 x 111 (phone)
(805) 899-3081 (fax)
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Lucie Spieler Sent: Wednesday, March 10, 2010 4:26 PM To: Steve Carlock Subject: RE: [Tessitura Technical Forum] Accidental Membership Deactivation
Yes, you can change the status on the back end. Change current_status from 8 (deactivated) to 2 (active). Be very careful to limit your update to the customer_no and cust_memb_no that you intend.
Lucie
I've always set the cur_record to equal 'Y' at the same time as changing the status.(as per helpdesk recommendation when I had submitted a ticket on something similar)You may want to check tx_cust_membership on that cust_memb_no to see if this updated since you changed the status.
What table(s) did you have to update to correct the issue?