ADA - ReserveTicketsEx - Special Requests

Doh. I saw that but read it as fixed in 11.0.3

You're saying a post 11.0.3 hot fix.

Big palm to forehead. Thanks. I'll give that a try!

Regards,
James Boncek

Sent from my iPhone

On Aug 31, 2012, at 9:33 AM, "Patrick FitzGerald" > wrote:


James--

This was actually broken in the initial v11 release, but fixed in the "Post v11.0.3 Hot Fixes" patch. Are you on the latest/greatest release?

Thanks,

Patrick
From: James Boncek >
Sent: 8/30/2012 3:36:38 PM

So, from what i understand, the generally accepted and designed way to do ADA best available is as follows and best put by Alan Levine. I arrived at the same conclusion in concept, but i'm yet to get it to successfully deliver the expected results.

"I just wanted to chime in and state that we have essentially implemented our ADA Ticketing using the methods Chuck describes below and it has worked incredibly well. The ability to use a specific hold code made all the difference. We are using it for wheelchair/companion seating, as well as sign-interpreted seating. We use Seat Types to designate actual wheelchair seats, but then we set all of the wheelchair seats and companion seats to the hold code. It allows us to seat those requiring wheelchair seats properly and get the best companion seats near them. We do allow patrons to select companion seats from unheld available inventory if there are not enough held companion seats nearby. We were also able to make it work not only on Best Seating but also in Select-Your-Own-Seat. Chuck and his team really came through in enabling us to meet the ADA requirements when they added the ability to specify a hold code and use held seats in Best Seating. We’re also able to handle situations where we have a special offer on seats in a particularl price zone, but have no wheelchair seats in that price zone. We can recognize that and allow the patron to purchase accessible seats in a different price zone, but at the price of the special offer. We’d be happy to review the details of all of this if anyone is interested."

As Alan explains, i'm using 1 Wheelchair SeatType in an Companion Hold in concunction with 3 regular SeatTypes in Companion Holds, all in 1 zone.

I should be able to exec ReserveTicketsEx with the following params:

1.
sWebSessionID:
QI0VS118X92O5HE056X7RPG5WYJ4DTNTKP24H8ND17R91QXSLPBJPJC8Y9VR5491
2.
sPriceType:
17
3.
iPerformanceNumber:
15160
4.
iNumberOfSeats:
4
5.
iZone:
1270
6.
sSpecialRequests:

WheelchairSeats=1andContiguousSeats=4andHoldCode=444andLeaveSingleSeats=Y

~~~

I would expect it to find, according to contiguity, 1 Wheelchair seat with 3 contiguous seats where all are held-breakable with code 444.
Problem is, i can't make it work! Anyone have any advice?
Thanks,
James





James Boncek
Project Manager

Carnegie Hall
881 Seventh Avenue, New York, NY 10019
Tel: 212-903-9747
Fax: 212-822-7700
jboncek@carnegiehall.org

[http://www.carnegiehall.org/common/imgs/chlogo2.gif]

carnegiehall.org | facebook | twitter | youtube | blog

Please consider the environment before printing this e-mail


________________________________

This E-mail and any attachments thereto is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. Dissemination, distribution or copying of this E-mail or the information herein by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you receive this E-mail in error please immediately notify me at 212-903-9600 and permanently destroy the original E-mail message, all copies, and any printout thereof.

[V.2007.0809.CARNEGIE.HALL.CORPORATION]

Yes, it is a little confusing--the fix wasn't in v11.0.3; there was a 'hotfix' a few weeks later.

Thanks,

Patrick

Okay, so i got a long weekend of rest and came back to the problem.  Verified that the Hotfix had been applied (it was), (WebAPI_hotfix_2378), and tried again.

The best i can conclude is that the functionality is less than i was expecting and understood, but also still not quite right.  

1:  If i only use 1 Special request parameter, HoldCode=444, it works.  and will only give me seats in 444.

2: If i pass in  HoldCode=444andLeaveSingleSeats=Y it gives me seats that aren't in a 444 holdcode!  This basic test is making it virtually unusable.  

Has anyone else experienced this or have they tested it and gotten results otherwise?

James

Okay, so i got a long weekend of rest and came back to the problem.  Verified that the Hotfix had been applied (it was), (WebAPI_hotfix_2378), and tried again.

The best i can conclude is that the functionality is less than i was expecting and understood, but also still not quite right.  

1:  If i only use 1 Special request parameter, HoldCode=444, it works.  and will only give me seats in 444.

2: If i pass in  HoldCode=444andLeaveSingleSeats=Y it gives me seats that aren't in a 444 holdcode!  This basic test is making it virtually unusable.  

Has anyone else experienced this or have they tested it and gotten results otherwise?

James

James, if you haven't already, may I suggest you put in a TASK ticket to get help on this and possibly also alert the Support and Development teams if there is an issue with the hotfix?

Best,

Todd