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!
Hi Kevin,
We have Current Membership Level set up as a user-defined element. JCA set it up for us. Our box office prints temporary membership cards (on ticket stock) for new membership purchasers or anyone who has lost their card and this allows us to put their level directly on the card.
Not sure how practical they are as they are pretty ACT specific but here are the ones we have
One to print the aisle number (kept in a custom table) for our theatre in the round.One to print a message when someones monthly ticket "membership" payments are late based on a constituency that is automatically maintained via sql job.(not to be confused with devo memberships)One to print number of parking sold in a package which prints on the header. (we print season tickets on normal ticket stock and have 3rd party parking vouchers)
I'm also going to be making one to print a message on the header for Will Call when an ID needs to be checked due to age discounts.
We have one for zone desc and one for zone short desc.
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 have three:
Full/Undiscounted Ticket Price
a "SUBSCRIBER" textbox is the purchaser is a Sub
a "GENERAL ADMISSION" textbox is the show is GA
We do use them and usually only to display static text such as VIP or Party depending on the price type and occasionally to change the name of the price zone or section. Although I do use it to display seat and row numbers or General admission depending the zone when I have a mixed performance between reserved and GA. One thing we do is that since there is only 6 elements is that I use an IF statements so each element can have multiple purposes. Such as if I have 4 different performances that each have their own static text I can use just one UDE instead of using 4.
Marty Jones
Database Administrator
Omaha Performing Arts 1200 Douglas Street
Omaha, Nebraska 68102
P 402.661.8469 | F 402.345.0222
Marty.Jones@omahaperformingarts.org
www.omahaperformingarts.org
For tickets, call Ticket Omaha at 402.345.0606
From: Kevin Sheehan <bounce-kevinsheehan4372@tessituranetwork.com>Sent: 4/7/2010 1:16:42 PM
Thanks everyone for the replies! They have been a great help.
-Kevin