I, in a rush, reversed a Friday and Saturday performance and put them in the wrong performance groups. We started seating in a new Hall before I discovered the error. I corrected the performance groups. When I go into one of the accts that have 1 Saturday performance in a Friday package or visa versa, rebuild the order in leve the seats in the wrong perfornance locked in the order, I could use some suggestions on how to fix this.
The changes you make to a performance group do not affect packages that have already been sold. You are going to have to return the package in the existing orders and then add the package back again.
Kevin Sheehan
Documentation & Learning Resources Specialist
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
Yes, I have done that, the problem I am running into is that the seats in the origional performance remain locked in the order even though, they do not show up in the subline items. If you can shedd any light on that I would realy aprreciate it.
Hi Andrew,
You probably have one of these utilities running nightly, but you might want to have your IT person try running it manually to see if it clears this issue up for you.I've supplied the documentation for both the old and new version of this utility.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’ 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.