Hello, i have had a gentleman on the phone saying that he tried to book his tickets online and it failed, so therefore he attempted to call us and book them. We told him the ususal line of they will release in 30 mins (which is normal for us), but when he called back a few hours later they are still purple and still under his name.
Is there anyway that you can release purple locked seats?
Jennie
We go to the seat map, click and drag over the seats to create a block selection, right click and select “Release Locked Seats”.
Jimmy
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Jennifer Sime Sent: Monday, August 16, 2010 9:40 AM To: Jimmy Godsey Subject: [Tessitura Ticketing Forum] Locked Seats
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
IF the seat has a db #, then the process from Footprints works well. We have four seats however that are "Locked" (green) and do not have a db#. How do I release those?
Have you tried running TP_CHECK_SEAT_STATUS_BATCH?Normally this would be a nightly scheduled job but I've used it at times to fix seat issues on the fly.
Here is the documentation for that as well as the older procedure which is referenced.
OLD - TP_CHECK_SEAT_STATUS: This procedure does a check of all seat records in the inventory, looking for any discrepancies that might be present. It automatically fixes any small discrepancies and reports each of these in a table called T_CHECK_SEAT_STATUS. The only type of error that this procedure does not remedy is when a seat appears in more than one order, which is a very rare occurrence. We recommend that this procedure be run nightly and the table checked occasionally. The parameters to the procedure are:• Season, a single season number from TR_SEASON • Fix_problems, a flag indicating whether the procedure is to automatically fix the discrepancies that it finds. The default is ‘N’, ‘Y’ sets auto_fix on.• Season_str, a comma-delimited list of season numbers from TR_SEASON. This parameter allows more than one season to be processed in a single run. By default this parameter is nullExamples: TP_CHECK_SEAT_STATUS @season = 3, @fix_problems = ‘Y’TP_CHECK_SEAT_STATUS @season = null, @fix_problems = ‘Y’, @season_str = ‘3,4’NEW - TP_CHECK_SEAT_STATUS_BATCH: This is a new version of TP_CHECK_SEAT_STATUS added in v9.0 that runs much faster as it is written without a cursor. It has all the same function and parameters as TP_CHECK_SEAT_STATUS (above) plus an additional parameter @skip_past_perfs, an integer value which tells the procedure to skip performances that have taken place n days ago. So, for example, if @skip_past_perfs = 7, then the procedures handles all perfs in the seasons whose perf_dt is greater than 7 days ago. If the parameter is set to 0 (the default) , the procedure processes all performances in the chosen seasons. This version is preferred over the older TP_CHECK_SEAT_STATUS.