Hello,
I've recently been trying to implement Order Imports. Currently we've been testing this within our Live to Test versions before attempting this with outside organizations. We've been encountering an error that is not clear or sensible and was wondering if anyone had any idea what this error could mean or what else could be the problem:
"Order 1 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 on..."
What is unclear is that I've attempted to do this in two ways, the first was using the seating range per customer, and received this. I figured a work around would be to run each seat as an individual order. I did this, copied the first seat into the last seat line so that the range was true. I, however, still received this error. I have no idea how or why a single seat, within the same map (this is a Live to Test import so it is a copy of our own map) would not be contiguous.
Does anyone have any idea or troubleshoot recommendations?
Thanks,
Maurice
Yep, definitely possible and expected to be able to import multiple sections in the same order. The problem that you saw is due to problems determining the number of seats when comparing the seat map with the range of seats provided in the import file for one of the data rows.
So if you tried to import “Row N 1-3 (2 Seats, oddly numbered)” and the seat map found Row N 1 to 3 actually contained three seats (seats 1,2,3), this data row would fail (and because this data failed the entire order).
The seat range also can’t contain more than one price zone. So if in the above example, seat 1 was Price Zone A and seat 2 was Price Zone B, the import doesn’t try to seat this. If you are running into these sort of issues, it’s very easy to import one seat per data row as there are far less integrity checks that have to happen.
Hope that helps.
+Ryan Creps
+Tessitura Network
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Amanda FreemanSent: Thursday, August 18, 2011 5:08 PMTo: Ryan CrepsSubject: Re: [Tessitura Ticketing Forum] Order Import Help
I think it should be possible to import seats from multiple sections into the same order. You just need multiple rows in the import file for that order, keeping the seats in the various sections in separate rows, but making sure the import_ref_no is the same for all the rows that are in the same order.
From: Maurice Nounou <bounce-mauricenounou6335@tessituranetwork.com>Sent: 8/18/2011 3:51:43 PM
I guess you are right, unfortunately I am trying to drop this into the same account, so everything should be built as the same order. Is this not possible then?
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing 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!
Okay, so I've used a few of the recommendations here and it has helped. I broke it up into multiple orders in order to make it so there would be no crossing of price zones, tried running it as a single line import and a grouped one. Unfortunately I'm still getting the error but only in a few locations. The majority of the report will run, but it will fail, no matter which way I work it, for the exact same row/seat combination. Currently I'm trying another import using a much more well sold show to see if this is something to do with those exact seats, is a larger section issue or anything else. I have arranged the spreadsheet so that it is in proper numerical order. The problem here is that it's not failing because the contiguity is off, nor should the seats be picking up an extra seat in between (though if there were a way to check this other than looking at the facilities manager and using the physical seat #, please advise) as this is occurring in the center of our orchestra where the seats are numbered 101-113 or whatever, as well as occasionally in sections with odd/even number seating. Furthermore I ran into a case where I am receiving this error for a single seat, I believe M 107, but no matter what I check I can't figure out how a line which is selling 1 seat, picking up 1 seat, is not contiguous or has too many seats in the request.
I appreciate all the input everyone's given me so far! Thank you!