We had a large batch of tickets get accidentally reprinted which invalidated the original ticket barcodes. So now if those patrons show up their tickets won't scan in. Is there a way to revert back to the original tickets, or allow access for certain tickets for scanning even though they are the older barcodes? This is a couple hundred tickets from multiple shows so we'd prefer to not have the patrons coming back to the ticket office, or having to send out the reprints.
It would nice to have a feature to load an order and revalidate a ticket or cancel out a printed ticket batch to revert back.
Thank you in advance for any help.
Edward Trevino
Eisemann Center
Richardson, TX
Oh, I feel your pain. This happened to me, and with the help of Tessi support I wrote up some SQL that for the most part (there were a few little weird instances) worked.
Basically the idea is (totally taken from my TASK ticket):
- Find all the Reprinted events in T_ORDER_SEAT_HIST with the batch_no of the Reprint. This will give you the order numbers you need to fix.- Knowing the orders, locate the Printed rows (the original printed rows) for each order in T_ORDER_SEAT_HIST. You would then need to update the ticket_no in T_SUB_LINEITEM to the ticket_no of the T_ORDER_SEAT_HIST row for the original printed event using the sli_no for the link.- In TX_SLI_TICKET, find and delete all the rows corresponding to the Reprinted ticket_no's for these orders.
Make the reprint table a permanent local table, that way you have an audit trail of sorts as to what was changed and what it was changed from. I also added another bit to remove any tickets that had been reprinted after the bad reprint batches in case there were legit reprints.
And most important. TEST TEST TEST. There were things I found and fixed by hand (however, I don't actually remember what the issues were, just that there were some). I'd also suggest opening up a help ticket as they are always loads of help.
I'm uploading the SQL I used to my profile if you want to take a look. Buyer beware, caveats galore, don't blame me if things break. :)
HTH,
Heather
Another option is you can run your scanners in offline mode. If you have the N-Scan number on your tickets you can still validate that the tickets are for the correct performance. But if you have the ticket number on the tickets, you will only be recording attendance. Heather’s suggestion is probably best, but if you can’t make that happen at least you have another option to head off all those invalid tickets.
Kevin Sheehan
Documentation & Learning Resources Specialist
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
Thanks for the help...I think Heather's way will be too complex for us to implement right now. It's completely user error for this happening, but the system should have a verification message for printing. There is both the Print Ticket and Print Order buttons on the same screen under Sub Line items and in a mad rush during show time it is easy to press the wrong one. It would be nice if the system would verify with a message, Do You Want to Print ALL X Amount of Tickets? YES/CANCEL
This happens to us all the time, and usually it is in small batches that we can just resend them out, but we have some clients with large Comp orders and people ask us to reprint specific tickets from them.
Also some way of undoing this beyond jumping into SQL stuff would be nice.
Cheers,
-Edward