web seat config opens and sub holds

Michael,

The web API cannot break hold codes.  There is no setting to change this.  If you are holding seats for subscriptions with hold codes you won't be able to sell shose seats on the web.

You have two options.  You could use allocation codes to hold your subscrtiption seats.  To do this you would set set the subscription allocation code so that you can only break through it when you are in the subscription mode of sale.  The only caveat here is that allocation codes are not displayed on the composite map for packages, so your staff would not see which seats are allocated when seating a package.  Here's a link to the Allocations document if you want to learn more about them: 

The other option you have is to set the web API to not seat package orders, and then your staff would go back and seat them later.

Thanks Kevin,

We currently have the web api set to not seat web orders.  We run a report and do that manually.  The problem has more to do with the radio button that the user uses to select the seating section for their sub purchase.  We have a large hall with lots of small seating sections.  When single sales break up the package so the same "open" seat is no longer available through the whole package the section shows on the web as being sold out.  We still have "sub" holds that hold the same seat all the way throught a package so that we can sell a fixed seat package but the web doesn't see these seats as available.  The web needs to "see" both open seats and sub holds as being available. 

When I ran into this same issue in a previous position it was a simple matter of adjusting some code or table.  I don't remember exactly where it is though...

Hi Michael,

We have seating flags set in our web config files to allow or disallow seating for packages or specific concerts.  I'm not sure that's helpful or not, but that's pretty much the end of my web config "expertise" (ha!).

Lesley

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.