Hey all!
Our standard ticket type has 5 lines of ticket text on it. Tessitura only offers 4 lines at the performance level so I hijacked the Performance Description line as my first line of text to make it 5. The only problem I've had with that so far is that it isn't always the performance name that goes into the first line of ticket text. But we've worked with it.
Our live website using the Tess web api has just been launched and suddenly my devious plan doesn't work. The Perf Description gets pulled onto the shopping cart. Great for some shows. Really not great for others.
I've been tasked with finding a different field that I can use to pull the first line of ticket text from instead. The kicker is that it has to be at the performance level (the other ticket text fields in titles, productions, production seasons won't work) but I can't find anywhere else at that level that I can pull on to the ticket.
I saw in the Data Elements that there is also Perf Long Title 1 and 2. These both appear to pull the Perf Description line. Do they actually exist as their own field somewhere else? Or does Tess actually have 3 data elements for the same field?
Thanks!
Could you create a content type specifically for that extra line of text you need and then use a user-defined ticket element to display it?
Hi Amanda (or any other followers!)
We set up the content line and have it successfully pulling onto the ticket text. However, I set up the ticket design to pull up to 50 characters but it's only pulling 30 characters.
Is there a limit restriction in a system table that I'm overlooking? I thought the content items had a very large character limit.
Thanks again
There is a data length field in the system table T_DESIGN_ELEMENT.
Thank you. I've updated that table and still no luck.
I am currently searching through the system tables looking for any other data length field I could have missed. Perhaps it would be easier to submit a support ticket at this point.
Unless there are any other thoughts from my wonderful Tessitura friends of course. :)
Beth-
I've dealt with this before. The limitation is not in the field or the definition in T_DESIGN_ELEMENT, but in the code that pulls the data, TP_GET_TICKET_ORDER_ELEMENTS. It defines ude_1 through ude_6 as varchar(30) fields and only gets 30 characters of each user-defined field, even if you've redefined the field length.I suspect this limit comes from the theoretical maximum characters printable on a standard 2x5.5-inch ticket using the larger Boca fonts.
I have found it necessary, in the past, to use multiple ude_ fields to define a long stretch of custom text.