Multiple PAH designs for same MOS

Thanks Chuck - I hadn't tried leaving the design column empty. Will do.
Mary




"Chuck Reif"

3941@tessituranet To
work.com> mmueller@lyricopera.org
Sent by: cc
"Tessitura
Ticketing Forum" Subject

@tessituranetwork Multiple PAH designs for same MOS
.com>


06/22/2010 02:22
PM


Please respond to
"Tessitura
Ticketing Forum"

@tessituranetwork
.com>






If you leave one row in the table for the MOS and leave the ticket_design
column empty, the process should use the design that is noted in
performance setup. I can't tell by your message whether you tried that
approach or not. Having two rows in the table is not the correct approach
for what you're trying to achieve.


From: Mary Mueller
Sent: 6/22/2010 1:24:51 PM
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.

NOTE: A PDF template must be created for each ticket design used.





This message was sent automatically to you by www.tessituranetwork.com
because you subscribed to the Tessitura Ticketing Forum. You may reply to
this message to post to the Ticketing 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!

Thanks Chuck - I hadn't tried leaving the design column empty. Will do.
Mary




"Chuck Reif"

3941@tessituranet To
work.com> mmueller@lyricopera.org
Sent by: cc
"Tessitura
Ticketing Forum" Subject

@tessituranetwork Multiple PAH designs for same MOS
.com>


06/22/2010 02:22
PM


Please respond to
"Tessitura
Ticketing Forum"

@tessituranetwork
.com>






If you leave one row in the table for the MOS and leave the ticket_design
column empty, the process should use the design that is noted in
performance setup. I can't tell by your message whether you tried that
approach or not. Having two rows in the table is not the correct approach
for what you're trying to achieve.


From: Mary Mueller
Sent: 6/22/2010 1:24:51 PM
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.

NOTE: A PDF template must be created for each ticket design used.





This message was sent automatically to you by www.tessituranetwork.com
because you subscribed to the Tessitura Ticketing Forum. You may reply to
this message to post to the Ticketing 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!