Re-naming a Membership Level

Here's a question: If I want to re-name a membership level (as in the three-character code), I know it needs to be changed in T_MEMB_LEVEL and TX_CUST_MEMBERSHIP (because you can’t change it in the front-end). But there’s a foreign key constraint that catches you if you change either one of those. Is there a quick and easy way to get around that?

 

Cheers,

 

 

Matt

  • Former Member
    Former Member $organization
    If it were me,  I'd delete the constraint make the changes and then add it back. Ugly. But it works. 
    
    Matthew Hodge <bounce-matthewhodge3604@tessituranetwork.com> wrote:
    
    

    Here's a question: If I want to re-name a membership level (as in the three-character code), I know it needs to be changed in T_MEMB_LEVEL and TX_CUST_MEMBERSHIP (because you can’t change it in the front-end). But there’s a foreign key constraint that catches you if you change either one of those. Is there a quick and easy way to get around that?

     

    Cheers,

     

     

    Matt




    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!
  • Hi Matt,

         I am in a similar situation and was wondering what you did?

    Arthur

  • Hi Matt,

        Theran MacNeil from Tessitura suggested the below which I am going to give a try.  I will let you know how I make out.

        ---Arthur

     

    Of course, if you have the SQL skills in-house, you could move all memberships that would be affected by the level code change out of TX_CUST_MEMBERSHIP and into a local table.  With these memberships out of TX_CUST_MEMBERSHIP, you would then be able to update the level code(s) on the membership level(s).  Then you would update the level codes on the memberships in your local table to the new value(s).  Once the level codes in the local table match the new values, you can insert the memberships from the local table back into TX_CUST_MEMBERSHIP.

  • When we renamed our levels, I inactivated the old levels & created new ones…

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Arthur Curtis
    Sent: Wednesday, May 06, 2015 7:26 AM
    To: Monica Martin
    Subject: Re: [Tessitura Technical Forum] Re-naming a Membership Level

     

    Hi Matt,

         I am in a similar situation and was wondering what you did?

    Arthur

    From: Matthew Hodge <bounce-matthewhodge3604@tessituranetwork.com>
    Sent: 12/1/2013 7:00:34 PM

    Here's a question: If I want to re-name a membership level (as in the three-character code), I know it needs to be changed in T_MEMB_LEVEL and TX_CUST_MEMBERSHIP (because you can’t change it in the front-end). But there’s a foreign key constraint that catches you if you change either one of those. Is there a quick and easy way to get around that?

     

    Cheers,

     

     

    Matt




    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!

  • I would not change the 3 letter codes. In either TX_CUST_MEMBERSHIP or T_MEMB_LEVEL.  Particularly if you have membership still active with the old codes.

     

    Also be careful about creating new member level codes.  The documentation notes that they must be unique for your entire system regardless of membership organization.  Some versions of the client did not enforce this uniqueness.

     

    --Tom

    718.724.8135

    tbrown@BAM.org

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Monica Martin
    Sent: Thursday, May 14, 2015 3:51 PM
    To: Thomas Brown
    Subject: RE: [Tessitura Technical Forum] Re-naming a Membership Level

     

    When we renamed our levels, I inactivated the old levels & created new ones…

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Arthur Curtis
    Sent: Wednesday, May 06, 2015 7:26 AM
    To: Monica Martin
    Subject: Re: [Tessitura Technical Forum] Re-naming a Membership Level

     

    Hi Matt,

         I am in a similar situation and was wondering what you did?

    Arthur

    From: Matthew Hodge <bounce-matthewhodge3604@tessituranetwork.com>
    Sent: 12/1/2013 7:00:34 PM

    Here's a question: If I want to re-name a membership level (as in the three-character code), I know it needs to be changed in T_MEMB_LEVEL and TX_CUST_MEMBERSHIP (because you can’t change it in the front-end). But there’s a foreign key constraint that catches you if you change either one of those. Is there a quick and easy way to get around that?

     

    Cheers,

     

     

    Matt




    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!




    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!