Hi all,
Just wondering if anyone has used this function yet. We're thinking of moving an entire show in one facility into a new facility. How has it worked for you? Is there anything that I need to consider (ie. unseat patrons, etc.) that I would have to do before starting the process?
Thanks in advance!
Hey there
We've used this functionality for just this purpose this past October. I would be more than happy to talk with you and help out as much as I can. Email me or call me
Jeffrey Cass
Ticket Services Manager
Chicago Shakespeare Theater
312-595-5638
Hi Jeffrey,
Yes please - I'll give you a call today! Thank you!
Hi,
I also have a problem with the section during order import.
Our stalls have 4 sections (one for each door). e.g. Stalls Door 1, Stalls Door 2, Stalls Door 3, Stalls Door 4.
I'm importing an order import file from an agent who has our venue setup in their software with all the stalls as one section.
This is causing a problem during the Ticket Order Import Utility run.
If I put a row in TR_IMPORT_SECTION_MATCHUP for "Stalls" to match "Stalls Door 1", it works for seats in that section but not the others.
Is there any way around this?
I'm thinking I may need to create a script to update the stalls section based on the seat number in TW_ORDER_IMPORT, and maybe put a exec to a local SP to this somewhere in the import process.
Any suggestions appriciated.
Sadly, this post came through email but didn't make it onto the site, so i'm recording it here. Back to the forum troubleshooting....
From Ryan Creps:
"This is an example of "one to many" that can’t be handled directly by the import. The import uses a combination of Section, Row and Seat to determine the unique seat_no within a facility. There is no way to map a single section description “Stalls, e.g.” to more than a single section using TR_IMPORT_SECTION_MATCHUP. This matchup table was designed for one-to-one matchup (“Orch Left” is named “OR LEFT” in our system) and many-to-one matchups (“Orch Left” and “Orch Right” from the import are mapped to “Orchestra”).
This is going to be an example of where you need to massage the data slightly before passing it to the Order Import. You can either do this manually or in a more automated fashion by bypassing the bulk load data import process that the utility uses.
There is information in the help documentation for this utility: http://www.tessituranetwork.com/Help_System/Content/Order%20Import/Order%20Import%20Technical%20Processing.htm
Start with the "NOTE:" section at the top of this page.
+Ryan Creps+Tessitura Network"