we have an issue with sub packages on the web... once singles go on sale the web packages (which looks at "open" seats) starts droping seating sections, showing them as "Sold Out" when there are tons of Sub holds. I've run in to this before and the solution was to adjust the web seat config (?) to look at both "Open" and "SUB" holds for packages. Can someone help me direct out Tech folks where to find this?
Hi Lesley, Good to hear from you! Hope all is well in St. Louis!
The problem isn’t with seating… (we run a report and manually seat) It is with what shows as available or more precisely what shows as sold out. The web needs to "see" both open seats and sub holds as being available.
Michael Granados
Oregon Symphony
Find us on Facebook
I think there are two different tables involved here:
tx_perf_hc and tx_perf_seat.
1, All seats are tx_perf_seat table.
2, if you put a hold code on a seat, it will create a record in tx_perf_hc table.
In this case, some of the sub holds should be removed from tx_perf_hc table, so I think what you need to do is create a sql job to clean up the tx_perf_hc table.
3, if your web open seats have special hold code, you should update those sub holds to web_open_holds, otherwise what you should do is deleting those sub holds form tx_perf_hc table.
4, tables need to have a look:
tx_perf_hc, t_hc, tx_perf_seat, tr_seat_status.
(there are triggers on tx_perf_hc table, they will process the update in tx_perf_seat table.)
So, I think all you need is a SQL job, not a web config file or a web API.
Please correct me if I am wrong.