Multiple PAH designs for same MOS

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 Night
id 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.