It seems like my nscan works with just the facility ID, but from what I understand it can work with the entry point for validation as well. But can you validate a ticket by the facility ID & the entry point at the same time?
And if it does validates both at the same time, what happens if i have both fields are filled in which field takes in case of a conflict.
EX. I have a ticket that has the facility ID and the Entry point (if that's possible). In tessitura Facility ID of 5 is theatre1 but the entry point (by mistake) was set to entrance of faciity 2 (theatre 2). What happens when the ticket gets scanned?
Hi John,
Yes, you can and should use facility ID and entry point together.
When you enter a facility ID in the unit profile, it updates the units with all performances in that facility on the current day. When you set up your entry points, you associate a section (from TR_SECTION) with an entry point ID (that you choose), and then you enter the entry point ID into the unit profile.
When a ticket is scanned it validates that it is for one of the performances currently on the unit and then looks at the seat assignment to find the section and sees if that section is associated with the entry point currently on the unit. If the unit has been programmed with the wrong entry point for the door it is used by (or the constituent just goes to the wrong door), then you’ll get an invalid ticket error which will specify the correct entry point for the seat location.
If you set up your entry points incorrectly, you can correct them at any time. Entry points are not printed on tickets; N-Scan just references which entry point is currently associated with the section for the ticket’s seat location at the time of scan. Facility ID is also not printed on tickets. The only information printed as a barcode on tickets is the ticket number (and if you use the N-Scan Number element the code also includes the performance number as a backup for offline scanning). At the time of the scan N-Scan looks up that ticket number to see if it is still valid, which performance it is associated with, and which seat location it is associated with.
I hope that helps. If you haven’t already, you should check out the N-Scan Application Guide for full details on N-Scan setup.
Kevin Sheehan
Senior Documentation & Learning Resources Specialist
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
I did read the guide and I think the part that's confusing is that in our TR_SECTION the "Section Legend" is only an letter code, the "Print Sequence" is a number code, and the "Print sequence" is empty. I can not use the Section legend in the NSCAN_ENTRANCE "section" column as it won't accept sletter. Does the NSCAN_ENTRANCE "ID" column have to match the ID in the TR_SECTION?