We trying to work through the steps and changes that may be needed to use the new Pricing Rules and two questions within Development seem to take us in circles
1) Virtual memberships -- memberships start the first of the next month so a person becoming a new member would be given a constituency that begins the first of the next month (true too for upgrades when constituencies change).
The rules says the constituency must be active -- based on the above the virtual membership will not work since membership/constituency will not be active until the next month.
TRUE or FALSE?
2) Pre-sales -- rather than discounts we tend to do more pre-sale for members. Since by definition prior to public sales -- it is possible to set a pricing rule that allows members to login and buy ahead of public sales.
Thanks for settling these debates!
Brian
Appreciate your willingness to reply and certainly acknowledge how nice having a SQL guru can be. In this case though there would not be a list yet – it would be virtual and no constituency or invalid constituency.
Would be great if someone could just let us know if we need to change our membership or not.
From: Brian Parker [mailto:bounce-brianparker6265@tessituranetwork.com] Sent: Wednesday, December 14, 2016 1:27 PM To: McKinley, Leslie <LMcKinley@nycitycenter.org> Subject: Re: [Tessitura Technical Forum] Pricing Rules: Pre-sale and virtual memberships
Leslie,
1.) My guess on this would be TRUE but I know that our SQL guru for our consortium set up a List Manager Criteria we've labeled Constituency* (ALL) which will pull anyone to a list that has had a specified (or a multi-selection of specified) Constituency even if it is no longer active. Obviously, this could have negative implications because you might pull people who shouldn't be promoted, but this might be one solution to a "virtual" membership that hasn't technically begun but should be active for ticketing.
Code:
Select Distinct a.customer_no
From V_CUSTOMER_WITH_PRIMARY_GROUP a WITH (NOLOCK)
JOIN (Select a1.customer_no From lxs_const_cust a1 WITH (NOLOCK) Where a1.constituency in (274)) as e ON e.customer_no = a.customer_no
Where IsNull(a.inactive, 1) = 1
2.) As far as I know this would also be TRUE. I believe you can set Constituent Criteria with a given Pricing Rule so you could set the on-sale date for that Pricing Rule to be prior to your public on-sale availability. We do this with our Center for Dance Education (kind of) by turning on our internal ability to sell tuition to classes before they are publicized on our TNEW page, so I'm assuming that Constituent Criteria could be a solution for a public TNEW on-sale. I'm admittedly not as seasoned on this, though.
Thank you,
From: Leslie McKinley <bounce-lesliemckinley4321@tessituranetwork.com> Sent: 12/14/2016 11:21:45 AM
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!