Hello all,
I’ve set up tr_paht_configuration with 2 rows for the same MOS. Each row corresponds to a different ticket design available.
To boil it down:
id 3 = MOS 24 design = Opening Nightid 4 = MOS 24 design = Opera Standard
So, if I have both an Opera Standard perf and the Opening Night perf in my shopping cart, shouldn’t each generate its own design? I have an Opening Night PAH design template and an Opera Standard PAH design template, and if I only have one of the perfs in my cart the correct PAH ticket is generated.
When the cart contains both it forces the Opera Standard data through the Opening Night design. If I switch the design in the table so that Opera Standard is id 3 and Opening Night is id 4 then the Opening Night perf data is forced through the Opera Standard design.
I understand the id hierarchy, but it doesn’t seem to be working right….what am I missing? I’m interpreting the snippet from the PAH documentation below to mean I can have as many PAH designs as there are ticket designs, no matter if they’re processed in the same order and therefore same MOS. But that’s not what’s actually happening.
Any ideas?
Thanks,Mary
From Tessitura_Print_At_Home_Ticketing _Service doc:
Ticket Design – A dropdown value from TR_DESIGN used when generating data for the delivered PDF. If this value is empty, the ticket will be generated from the ticket design specified in the performance’s pricing setup.
NOTE: A PDF template must be created for each ticket design used.
Hi Mary,
Perhaps the documentation needs some clarification. If the same mode of sale is present in more than one row in the table, the row with the highest ID always wins. That means that the second row will never get used. In other words, you really shouldn’t have the same mode of sale present in more than one row. If you need to us different ticket designs depending on which performances are in the basket, you should have one row in TR_PAHT_CONFIGURATION with the Ticket Design column left blank. Then it will use whatever ticket design is set up on the performance for the price type used.
This functionality is intended to allow you to override the regular ticket designs with different PAH ticket designs, but you can only do it on an order level based on MOS, not on the performance or price type level. Are you using different Tessitura ticket designs for PAH and regular tickets? If not, then you shouldn’t have any problems if you leave the Ticket Design column blank. If you are, why? Was it deliberate because there is some additional data you are pulling for your PAH tickets? I only ask that because it is not required to create a new ticket design just for PAH tickets. So if you only did it because you thought you had to, then you can change your PDF templates to use your regular ticket designs and then be able to choose the design based on the performance not the MOS. Does that make all make sense?
Kevin Sheehan
Documentation & Learning Resources Specialist
Tessitura Network
1 888 643 5778 ext 329 Office
ksheehan@tessituranetwork.com