We are planning a program that includes 2 timed entry events during a 4 hour window. One of the timed entries is offered every 15 minutes (a historic house tour) while the other performance is offered two times (6:30 and 8:00). Pending which performance the patron selects, they will not be able to tour the house during certain times. Has anyone built an event in TNEW v7 that hides times for one program when a specific time for another program is selected, or know if this is an option? We are relatively new and appreciate all suggestions. Thanks!
Ashley,
If I read you right, you are talking about a situation where ANY sales to Performance A means that Performance B needs to go off sale, is that correct? Would vice versa be true as well? That is, ANY sales to Performance B means that Performance A needs to go off sale, too.
This CAN be done, but it will involve some custom work. We have something that we are announcing today actually involves four different events on one day, 3 in one group, 1 on its own, and the purchase of any one of these events forces the events in the other group off sale (so purchase of any one of the 3 turns off the other 1, and purchase of the 1 turns off all three of the other performances).
Basically, what ended up happening is that I had to create two keywords, that I called "Toggle Group 1" and "Toggle Group 2" which were applied to each group of performances every day. I then put a form on each one, and in this case, there are conveniently some FYI type language we needed to get to patrons anyway, so we just have a checkbox saying "I Understand" that patrons have to check to purchase that event, no big deal. But the important thing is that there IS a form, which we then use to, instead of creating a CSI or storing some information in some custom tab, we then wrote a custom procedure to turn off sale all the events that day in the other toggle group.
If you are interested in this sort of solution, I am more than happy to share the experience. It WAS a bit of work to get there in the end. But if this is something that is going to be ongoing for your organization, it might be worth the time investment. Depending upon what count of ticket sales you need per event to engage such a toggle, could also affect the coding needed. The particulars of our specific need only required one single sale per performance to enact the toggle.
If there is some other, non-custom way to make this work, I would love to hear it (even though it would render all the work I did null and void).
John