We have a facility in which there are 2 main sections, one section is general admission only and the other is reserved. Our ticket design displays zone, seat row and seat number. Is anyone using an if/then masking statement on their ticket design that says...if the section = A, then do not display seat row and seat number?
I'm assuming that this would live in the mask for the seat row and seat number element. If anyone has this, could you share?
We are constantly having to explain to people why a seat row and number appear on their GA tickets in this facility.
-Becci TN PAC
I had this situation once and handled it with a custom ticket element. So instead of having Row on the tickets, it was this element, which displays "GA" if the zone were the zone that's GA, and the actual row for all other zones. We choose to continue to display a seat number because we don't have N-scan yet and wanted a visual way to distinguish the tickets as different seats, even if they're not specific seats. But the theory was it was there was enough language during the purchase process telling the patron they were purchasing tickets in a GA zone that it'd be clear enough for them to have tickets saying "GA 7", "GA 8". If you wanted to get rid of the seat numbers you could either use an additional custom element that displays " " if the section is the one in question, or have just one element that displays both row and seat (or not) conditionally on the zone/section.
We also once had a different situation where we had two rows of GA seating, but they were the same section and zone, but we DID want to distinguish between these two rows; people were purchasing for any seat in the row, but which row it was mattered. I think it that case I ended up setting the actual row labels to GAA and GAB or something to that effect. Depending on your situation, it might be a shortcut to just change the row description to "GA" for the seats in question.
Hi Becci
you can try this simple masking code. I use this a lot and has come in very handy over the years.
case(trim(val) When 'A' Then ' ' else val)
This will print nothing if the text is A.
Cheers
David
Following up on this thread - I am trying to mask several possible data points (for example, if row A, B, C, D or E, then ' ' else val).
However, I'm running into the situation where I am running out of room in the masking element. Does anyone know an easy way to mask multiple possible data points? For example, can I use % to identify any value? Like seat number 1%% to identify any seat numbers in the 101 sequence?
Thanks!
Kim,
In your statement, are you saying [If A Then '' If B Then '' ... If E Then '' Else val]? I am not sure if this has changed with the version upgrade, but you used to be able to just say [If A,B,C,D,E Then '' Else val] inside the mask field operating as one big "or" clause for those five options A through E to then all result in the output of the desired ''. We used to use a mask like that on one of our ticket designs. That might help save you some space.
Hopefully that helps. Good luck!
John A. Moskal II
IIRC, the syntax and functions available in ticket data masking are Infomaker expressions.
A while ago I excerpted the Infomaker expression reference from the full documentation and put it on my profile: InfoMaker Expression Reference. Digging into that could help to reveal what's possible and what the limits are.
Ancient Thread Resurrection!
Anyway, I was digging through the current Infomaker Expression Reference (I think?) and was trying to make sure that LIKE would work, but I've been unable to get it to work (e.g. "IF((val like '%ucb%stud%'), '****ID Required at Door****', '')").
https://docs.appeon.com/im2022/imug/ch23s02.html
My sense is that the expressions/functions available in various Tessitura "Powerbuilder" components are capriciously constrained, and perhaps it is just "arithmetic" operators in ticket masks, but maybe I'm missing something subtle?