I'm wondering if anyone else has ever experienced this, and can hopefully help shed some light. On the rarest of occasions, inevitably once every few months, when our FOH is scanning at the door for a performance that is scanning without issue, a ticket for the correct show will trigger one of the very first performances we build when going live with Tessitura back in 2007. A quick scan a second time and the ticket scans no problem. Here are some of my thoughts:
- we are using the Ticket No data element as the barcode; we've had no other issues with using this, but should we switch to using the N-Scan Number element?
- there is no entry for Doors Open and Doors Close for performances that season as we were using NScan then. I'm wondering if I should just put values in there now?
Again, any insight would be greatly appreciated.
Thanks,Steve
I have had this happen. I have no idea how to fix it but figure if it is rare and random, I'm not going to change what is working 99.99% of the time. Hawana Hawana Townsley House Manager Charles W. Eisemann Center 972-744-4616 direct 214-906-4990 cell Volunteer Link for Scheduling: https://www.volgistics.com/ex/portal.dll/?FROM=21043 "Steve Lang" ---01/08/2014 04:08:28 PM---I'm wondering if anyone else has ever experienced this, and can hopefully help shed some light. On From:"Steve Lang" <bounce-stevelang5708@tessituranetwork.com> To:hawana.townsley@cor.gov, Date:01/08/2014 04:08 PM Subject:[N-Scan] Scanners randomly coming up with very old performance Sent by:N-Scan <groups-n-scan@tessituranetwork.com>
Thanks, Steve