Hi everyone,
My organization is part of a consortium, and another member org also sells tickets for us. We recently redesigned our ticket stock, and thus our ticket designs as well, but ran into an issue. The other organization uses their own ticket stock, which doesn't align with ours, and so seating information becomes difficult to read for ushers when the guests have tickets printed by the other org.
Short of creating a second entire set of prices and associated designs for the other organization, can anyone think of a way to solve this problem?
I wonder if you could solve this by getting really clever with the custom ticket design elements you can output by modifying the LP_TICKET_ELEMENTS stored procedure. Theoretically you could tie back to the organization through the order (and maybe one or two other joins) and use that to determine the content in each of the six custom elements in your design. Custom 1, for instance, could dynamically output the performance date and time for Organization A but the customer's name (or nothing at all!) for Organization B.