User Defined Data Elements for Ticket Designs

We put one together to print notes from the order notes field on our will call headers.  There are specific characters that start and end the printed notes.  It allows us to have tickets left under another name, or ask for coupons or vouchers as they are needed (while not printing notes that don't pertain to the performance).

We put one together to print notes from the order notes field on our will call headers.  There are specific characters that start and end the printed notes.  It allows us to have tickets left under another name, or ask for coupons or vouchers as they are needed (while not printing notes that don't pertain to the performance).

Are you using any of the user-defined data elements on your ticket designs?  I'm currently working on a new ticket design document and I'm looking for some practical examples of what data people are retrieving with these elements.  If you are using them, please reply to this thread and share what data you are retrieving.  No code from the stored procedure required, just which data you are printing on the tickets.

Thanks!

We put one together to print notes from the order notes field on our will call headers.  There are specific characters that start and end the printed notes.  It allows us to have tickets left under another name, or ask for coupons or vouchers as they are needed (while not printing notes that don't pertain to the performance).

Are you using any of the user-defined data elements on your ticket designs?  I'm currently working on a new ticket design document and I'm looking for some practical examples of what data people are retrieving with these elements.  If you are using them, please reply to this thread and share what data you are retrieving.  No code from the stored procedure required, just which data you are printing on the tickets.

Thanks!