order import utility

I am using the order import utility for the first time and in the process of preparing my file.

The data I have comes from another Tessitura user organization that used the order export utility to create the file for us.

I'm seeing some discrepancies in the number of seats column and I'm not sure if they're actual errors or if there is an explanation.

Here's an example:

seat start=10, seat end = 24, number of seats = 4

In this particular venue the seat numbers go up by 2 so if the start is 10 and end is 24, I count 8 seats.

For most of the rows the number of seats is correct but I'm seeing a few hundred discrepancies in a spreadsheet of several thousand rows.  

Is there an explanation for this?  Is this something I need to fix before the import?

Dale

Parents
  • I can’t speak entirely because I don’t have all of the factors at play here, but I can say that the export utility uses seat contiguity to determine seat ranges.  This is how it avoids miscounting when seat ranges contain only even/odd seat numbers, for instance.  However, if their contiguity is not set up properly (or logically), then you could possibly be getting some odd results.  I would ask the other facility to run the “Check Completedness” report on the Seat Map in question in Facility Manager.  It would pull up some common bad-design issues like dupe contiguity rows/seats.

     

    Amanda’s suggestion of running the export as a single seat per row would eliminate this issue as well.

     

    +Ryan Creps

    +Tessitura Network

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Amanda Freeman
    Sent: Tuesday, April 10, 2012 11:46 AM
    To: Ryan Creps
    Subject: Re: [Tessitura Technical Forum] order import utility

     

    I haven't dealt with this specific scenario, this is just off the top of my head and might be totally off base, but we do occasionally have some people with say 4 seats in the same row, but they're not contiguous, a pair here, a pair there. I would have expected the export to show two lines for such an order, one for each pair, but could that be the case with some of those orders? Have you checked on any specific example orders with the exporting org to see if there were actually 4 or 8 seats?

    It might be a workaround to ask the org to re-export it with single seats output instead of seat ranges? 

    From: Dale Aucoin <bounce-daleaucoin4707@tessituranetwork.com>
    Sent: 4/10/2012 10:27:30 AM

    I am using the order import utility for the first time and in the process of preparing my file.

    The data I have comes from another Tessitura user organization that used the order export utility to create the file for us.

    I'm seeing some discrepancies in the number of seats column and I'm not sure if they're actual errors or if there is an explanation.

    Here's an example:

    seat start=10, seat end = 24, number of seats = 4

    In this particular venue the seat numbers go up by 2 so if the start is 10 and end is 24, I count 8 seats.

    For most of the rows the number of seats is correct but I'm seeing a few hundred discrepancies in a spreadsheet of several thousand rows.  

    Is there an explanation for this?  Is this something I need to fix before the import?

    Dale




    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!

Reply
  • I can’t speak entirely because I don’t have all of the factors at play here, but I can say that the export utility uses seat contiguity to determine seat ranges.  This is how it avoids miscounting when seat ranges contain only even/odd seat numbers, for instance.  However, if their contiguity is not set up properly (or logically), then you could possibly be getting some odd results.  I would ask the other facility to run the “Check Completedness” report on the Seat Map in question in Facility Manager.  It would pull up some common bad-design issues like dupe contiguity rows/seats.

     

    Amanda’s suggestion of running the export as a single seat per row would eliminate this issue as well.

     

    +Ryan Creps

    +Tessitura Network

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Amanda Freeman
    Sent: Tuesday, April 10, 2012 11:46 AM
    To: Ryan Creps
    Subject: Re: [Tessitura Technical Forum] order import utility

     

    I haven't dealt with this specific scenario, this is just off the top of my head and might be totally off base, but we do occasionally have some people with say 4 seats in the same row, but they're not contiguous, a pair here, a pair there. I would have expected the export to show two lines for such an order, one for each pair, but could that be the case with some of those orders? Have you checked on any specific example orders with the exporting org to see if there were actually 4 or 8 seats?

    It might be a workaround to ask the org to re-export it with single seats output instead of seat ranges? 

    From: Dale Aucoin <bounce-daleaucoin4707@tessituranetwork.com>
    Sent: 4/10/2012 10:27:30 AM

    I am using the order import utility for the first time and in the process of preparing my file.

    The data I have comes from another Tessitura user organization that used the order export utility to create the file for us.

    I'm seeing some discrepancies in the number of seats column and I'm not sure if they're actual errors or if there is an explanation.

    Here's an example:

    seat start=10, seat end = 24, number of seats = 4

    In this particular venue the seat numbers go up by 2 so if the start is 10 and end is 24, I count 8 seats.

    For most of the rows the number of seats is correct but I'm seeing a few hundred discrepancies in a spreadsheet of several thousand rows.  

    Is there an explanation for this?  Is this something I need to fix before the import?

    Dale




    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!

Children
No Data