• Replies 9 replies
  • Subscribers 336 subscribers
  • Views 105 views
  • Users 0 members are here
Related

Increasing prices on a Member Org on FY Changeover

Eric Oliphant
$organization

We are looking to increase our level-first membership prices on Oct 1. I think I want to change the ranges of the current membership org so that renewals/history stays intact, vs. creating a new Member Org. The level info is staying the same. 

However, we have a month and a half of membership renewals happening before the FY ends, so the current org needs to remain. Does someone need to manually update the levels on the org on October 1? How do I manage this transition? Fun addition, I will be out of the office on parental leave during this time, so I'll need to enlist/train someone to make this change manually, if necessary.  

Parents
  • $organization

    Eric,

    We are doing the same thing on Sept. 1st. I plan on having this all automated.

     If you have someone that knows SSMS, they could do the following (in TEST/DEV first).

     Create a new Local Table.

      1. By following the directions here: Tessitura v15 Help System - Local Tables (tessituranetwork.com)
      2. Name the table with a “LTR” at the beginning of it.
        1. LTR_NEW_MEMBERSHIP_PRICES (or whatever you want) with columns that mimics [dbo].[T_MEMB_LEVEL].
        2. It should also have columns of with something similar to new_start_amt, new_end_amt, and price_change_dt.

     Make the new Local Table show up in your System Tables (Reference Tables in V16) by using the directions in the Local Tables link above.

      1. Grant specific user group(s) rights to make changes to the system/reference table.

     Schedule a SQL Job to run when you want the price change to occur.

      1. The SQL Job references the new Local Table.

     This would result in allowing your membership staff to schedule the price changes within a system/reference table. All your CRM Admin would need to do is schedule the SQL Job each time you wanted to do a price change. As always, do this in Test/Dev first as a proof of concept before you attempt it in your Live/Prod environment.

     We also have a system/reference table that controls the membership prices on our TNEW website. Automating that one to change at midnight is the higher prioity. I’ll have another SQL Job update that one at midnight and the other Job update the prices in [dbo].[T_MEMB_LEVEL].

Reply
  • $organization

    Eric,

    We are doing the same thing on Sept. 1st. I plan on having this all automated.

     If you have someone that knows SSMS, they could do the following (in TEST/DEV first).

     Create a new Local Table.

      1. By following the directions here: Tessitura v15 Help System - Local Tables (tessituranetwork.com)
      2. Name the table with a “LTR” at the beginning of it.
        1. LTR_NEW_MEMBERSHIP_PRICES (or whatever you want) with columns that mimics [dbo].[T_MEMB_LEVEL].
        2. It should also have columns of with something similar to new_start_amt, new_end_amt, and price_change_dt.

     Make the new Local Table show up in your System Tables (Reference Tables in V16) by using the directions in the Local Tables link above.

      1. Grant specific user group(s) rights to make changes to the system/reference table.

     Schedule a SQL Job to run when you want the price change to occur.

      1. The SQL Job references the new Local Table.

     This would result in allowing your membership staff to schedule the price changes within a system/reference table. All your CRM Admin would need to do is schedule the SQL Job each time you wanted to do a price change. As always, do this in Test/Dev first as a proof of concept before you attempt it in your Live/Prod environment.

     We also have a system/reference table that controls the membership prices on our TNEW website. Automating that one to change at midnight is the higher prioity. I’ll have another SQL Job update that one at midnight and the other Job update the prices in [dbo].[T_MEMB_LEVEL].

Children
No Data