• Replies 4 replies
  • Subscribers 414 subscribers
  • Views 70 views
  • Users 0 members are here
Related

Rankings-MOS Shift for Member & Contributing Member

Lidija Stojanovic
$organization

Hello, 

I am needing some guidance on setting up ranking to trigger a MOS shift for our contributing members. Our current setup is:

  • We have a MOS called Member that triggers TNEW MOS shift for all accounts with active memberships
  • TR_RANK_TYPE = Member Ranking 
  • TR_WEB_RANKING = Member Ranking, Start Rank=100, End Rank=200, MOS=Member
  • LP_CUSTOMER_RANK procedure is running to update constituent rankings automatically
  • Every constituent record with an active membership has a ranking of either 100 or 200.
  • Values in LTR_CONSTITUENCY_RANKS defines ranking for constituencies. Our contributing members have a rank value of 200, and non contributing get 100 (total of 24 constituencies)

We are wanting to setup a MOS shift on TNEW for our contributing members in order to give them early registration access. I tried to set this up in TEST, but it was not working as expected. Here's what I did: 

  1. Set up a Contributing Member Mode of Sale. I made sure all the other MOS setup tabs were correct. 
  2. Added the Contributing Member MOS to a performance. Inactivated all other Modes of Sale on the performance.
  3. Added Contributing Member Ranking to TR_RANK_TYPE
  4. Added Contributing Member Ranking to TR_WEB_RANKING and set MOS to Contributing Member. Set the start rank to 200, end rank to 299. 
  5. In same table--for the existing Member Ranking, set start rank to 100 and end rank to 199. 

When I went to our Test site and logged in as a contributing member, I could not purchase tickets for the selected performance. 

What am I missing? Any help on this would be greatly appreciated! 

Parents
  • $organization

    I could've missed it in your explanation, but I think the LOWER the number, the HIGHER the ranking. We use a separate MOS for each separation of rankings (the greater access MOS has a lower number in the rankings table). I think the way you explained it, you are sending them both to the same MOS. Also, are the price type(s) available to that MOS?

  • $organization in reply to Neil Cole

    Hi Neil, 

    Yes, it looks like we were sending them both to the same MOS. The values originally put into LTR_CONSTITUENCY_RANKS were incorrect. We did not have a unique combination for each constituency, so it wasn't recognizing different rankings. 

    Thanks for your help! 

Reply Children