Apologies if this has been responded to before - but I couldn't find anything.
We have an issue with data we're getting from a third party and it appears to be caused by a problem with section matching where the seats in the string are in two different sections.
For example, in row A in the Stalls there are 40 seats A1:40. A1:20 are in the section named "Stalls Door 1" and A21:40 are in the section named "Stalls Door 3". In the provided data, seats A19:22 appear as one row, so the same section name is applicable to all seats. This causes the error "Order 53 skipped : Error 50000, Severity 0, State 0, Procedure , Line 0, The number of seats does not match the number of contiguous seats to be imported for one or more rows. Order will be skipped."
I can map incorrect door numbers without error via TR_IMPORT_SECTION_MATCHUP but this only appears to work if the whole string of seats are in the same section in Tessitura.
It is not possible to get the data from the other party with the rows split between the sections as their process is that the door number is identified by the first seat in the string and then applied to all seats in the string - regardless of which door ID is allocated to the other seats in the string.
Has anyone else come across this - and better still solved it? As ever, all suggestions gratefully received!
Martin
Can you have them send the data as individual seats instead of ranges?
The Order Import needs to be able to uniquely identify ranges of seats using only the information provided matched against the underlying contiguity. Because Section is the top level “group” for the seat range, there is really no way to do this. Otherwise, the utility would be making unreliable assumptions about the seat locations or quantity without the ability to validate using seat data.
+Ryan Creps
+Tessitura Network
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Martin Keen Sent: Monday, July 29, 2013 10:48 PM To: Ryan Creps Subject: [Tessitura Technical Forum] Order Import error - section matching/contiguous seats
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Ryan,
Thanks for the response. Sadly, it appears that we cannot at present get the data supplied as 1 seat per row.
We are requesting that we get a custom extract written for us. The third party is Ticketmaster - surely someone else has run across this issue with their data before - or is it because we have our facility built peculiarly?
Hi Martin
You could of course write some clever code that takes the rows as supplied, expands the seat range to individual seats based on the sequence, then re-allocates them to their correct section?
You'd probably need to do it with a cursor, but it shouldn't be that hard, assuming the ranges don't cross rows?
Ken