Hi all,
Have seen a few similar posts from years ago, so just seeing if anyone has come up with a super solution for this question!?
We currently use the same PAH ticket design for all of our events. In the TR_PAHT_Configuration system table it is setup as the wildcard, so all performances use this PAHT design.
However, the design purposefully does not include a seat number, as normally all our events (those since we implemented PAHT) are sold as general admission.
We now have an event that is going to be allocated seating, so want the seat number to appear on the PAHT.
What we would like to happen would be to have all our performances use the wildcard design, except this one performance. It seems that you can only make that happen by having a separate MOS or new price types specific to this performance?
We may also have the situation of people purchasing two events, one with allocated seating and one without, so in theory it would be two different designs.
Is there another solution or something we’ve missed?
Thanks,
Alison
Not too sure if this helps, but I believe we have the Ticket Design value in TR_PAHT_CONFIGURATION empty, so all ticket designs are linked to the price-type per performance in ticketing setup.
From the docs: "Ticket Design – The ticket design that will be used when generating data for the delivered PDF. If this value is empty, the ticket data will be generated from the ticket design specified in the performance’s pricing setup."
The main benefit of this approach is that we use the same MOS and price types, without having to create a whole separate MOS just for a different ticket design.
The limitation of this is that if you use a variety of BOCA designs, then you would need a corresponding PAHT template for each of these.
We currently use four designs for different kinds of standard events and whether or not we want to show the venue / GST status, and then a one off design for each paid exhibition. We're in the process of working out how to reduce this down to one design with some SQL masking, though.
Thanks for your responses. The blank seat number in a facility is a great trick to know, for when we’re building new facilities in the future!
We resolved the issue in the end by utilizing the User Defined Elements on our PAH ticket design & a local procedure, which references the specific performance, that we required the Seat No & Row No to appear on the PAHT delivered to the purchaser. Our IT whiz found the solution somewhere in the wonderful world of TASK Knowledge Base and implemented it successfully!