Originally Posted by
percysmith
[Search once using the Unelevated search first, and then use the batch search. Seems to fix the nil return problem.]
Ah, yes. I should make that more clear, or see if I can disable the batch button when the search was triggered by the website’s own search. The reason for this limitation is that the site uses the "flexible dates" search flag by default, and the unelevated one searches with it turned off. Since the unelevated search relies on checksums that the actual CX engine leaves on the page, a batch search using the altered parameters will not match the checksums and will fail.
Originally Posted by
Spacetek13
Has anyone been successful in getting a connecting itinerary to ticket using this tool? Got as far as inputting passenger details for my trip but since when using the site's own multicity tool the same itinerary errored out with some sort of Y inventory error I was worried I'd be out my points and not actually ticket.
If you can get to that page, it is unlikely there will be a problem.
To be frank, I’d be more surprised to see the multi-city tool not erroring out on most itineraries.
Originally Posted by
Spacetek13
What was weird with my booking is that the UnElevated tool was able to get the segments to go together but I got the "Redemption Class Y" error when doing the multi-city. Makes me worry that the bookings won't actually work in the end when using the tool. For reference I was doing LAX-LHR-BUD next summer.
I have no certain answer for this, but my hypothesis is that it could be related to the way the segments are coded when using the multi-city tools. Keep in mind that the multicity is a leftover from the era when we could book actual stopovers using the tool. My guess is that they are still coded as a stopover and not a transfer, and some arcane ticketing rule is blocking those itineraries from being ticketed as stopovers.