Is it possible for a ticket design element to reference the data value from another design element to decide on how to mask?
For instance, we have a facility that has several different types of seating sections. For most of the seats, even reserved seats we only want the ticket to print the seat row (in this case it represents a table/booth or a General admission seating area). However, this facility also has seated rows up near that stage that require unique seat numbers. My hope was to add the seat number to the ticket design, but add a mask that would print an empty string based on the value from a completely different data element, such as section.
Is something like that possible? Or would we need to have to try to setup some kind of custom user-defined element?
Hi Jesse! I don't think the seat element mask can reference values from other fields. Not sure how far along you are in your process, but there are a few things you could try.
If you're able to edit your facility, you can define those assigned seats near the stage with values that are never applied to the unassigned seats (such as using letters vs numbers, or a range of numbers significantly higher than the other seat values.) Then your mask can use logic to hide the seat value for those within the unassigned range.
Alternately, if the seats near the stage are a different price type, you could add a second ticket design that includes the seat location and associate it with that price type on your events.
We've already used this facility twice and it has an SYOS map attached to it. But we haven't built the upcoming shows so we could make changes to the facility before we start building it. We probably would want to leave the seat setup for the seated rows alone but we could add a 'T', 'B', or 'G', to the seat numbers for the tables, booths, and GA seats. If we made the other seats alphanumeric, do you know if the masking formulas accept a 'like' operator in the if/case statements?