Has anyone exported a show out of a fixed season order into a new order to switch the facility. What kind of issues did people run into with reporting, or possible double reporting of revenue?
I’ve done the whole performance release and the monies went back to on account just fine.
Nichole Mines
Ticketing Data Manager
1326 5th Ave
Seattle Wa 98101
From: Tessitura Ticketing [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Amanda FreemanSent: Friday, December 09, 2011 11:39 AMTo: Nichole MinesSubject: RE: [Tessitura Ticketing] Import/export and reporting
Hey Ryan,
I wondering, is there something special about On Account pmt method types that make them a bad idea/not work in this scenario? I mean, other than that the utility was written to exclude that type? is there something else that goes on when an on account payment is made that doesn't happen with other payment methods that the means by which the utility "pays" wouldn't cover, so it had to be excluded?
From: Ryan Creps <bounce-ryancreps9649@tessituranetwork.com>Sent: 5/12/2011 9:18:17 AM
The Order Import Utility, unfortunately, only takes the following payment types:
Check(3), Cash(5), Adjustment(6), or Other(7)
Unfortunately, as it stands, no on account.
-Ryan
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Kevin SheehanSent: Thursday, May 12, 2011 10:02 AMTo: Ryan CrepsSubject: RE: [Tessitura Ticketing Forum] Import/export and reporting
Actually, there is a magical way to refund the original performance. You can use the Performance Seat Release utility, which will return all seats and put the money on account. So you would run that after you do your export.
I’m not sure about using an On Account payment method in an order import. It probably would work. Ryan, do you see any reason why it wouldn’t work?
Kevin Sheehan
Senior Documentation & Learning Resources Specialist
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Marty JonesSent: Thursday, May 12, 2011 9:42 AMTo: Kevin SheehanSubject: RE: [Tessitura Ticketing Forum] Import/export and reporting
Peter,
When you export, all you are doing is taking a copy of the information from the original performance. The export will not change anything in the original orders or performance.
Now with the import and as long as you are not talking about the new orders being part of a rollover, you would just import into the real performance.
There is no magical way to cancel/refund the original performance. You will have to touch each order and do the return from there.
These are the steps that I would do.
1. Export the original performance to Excel
2. Return the seats in each order and put the money on account
3. Modify the seats in the Excel file to match the new facility.
4. Import the Excel file into the new facility using the on account money payment method
<insert disclaimer here!> I have not done tried a import using On Account payment methods so not positive if this would work or not. Hopefully, someone from Tessitura can vouch for this.
If all of this is for a rollover, then this will change how you would do this and I can go into detail if this is the case.
Hope this helps,
Marty Jones
Director of Information Services
Omaha Performing Arts1200 Douglas Street
Omaha, Nebraska 68102
P 402.661.8469
Marty.Jones@omahaperformingarts.org
www.omahaperformingarts.org
For tickets, call Ticket Omaha at 402.345.0606
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Peter NelsonSent: Thursday, May 12, 2011 12:23 AMTo: Martin A. JonesSubject: RE: [Tessitura Ticketing Forum] Import/export and reporting
Hi Marty
I have a related question. We have a run of perfs we want to move from one GA facility to another.
I was going to try using Import/Export works but I'm unclear what happens (if anything) to the 'exported' order in the original perf and how payments are handled so i would be interested to hear from anyone who has tried this scenario.
It feels like we're going to end up with a copy of the original perf but all the original data including payments remains in that perf? And should i be using a dummy payment method in the import set - if you use a 'real' payment method does that generate a posting?
Otherwise is there some other means of cancelling/refunding all orders in a perf and re-creating them in a new facility/perf?
From: Marty Jones <bounce-martyjones7649@tessituranetwork.com>Sent: 5/10/2011 12:53:01 PM
We just got done doing this. We created a dummy season. In that season we created a dummy performance that used the new facility. Export out of the original performance into excel modify the seats to their new locations if the current rows or seats between the new and old facility do not match. Then do the import. We then rolled from the dummy performance into the new subscription.
If you are using price type mapping between the two packages, I would just drop a comp price map onto each price type in the dummy performance.
Another option using the same dummy setup as above, is to manually seat the patrons into the dummy performance instead of doing the export and then do the rollover. I would do this route if there isn't a ton of subscribers.
By doing this in a dummy season and performance, it is easy to separate out that this not real revenue and does not show up under any real season's reports.
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Nichole MinesSent: Tuesday, May 10, 2011 11:42 AMTo: Martin A. JonesSubject: [Tessitura Ticketing Forum] Import/export and reporting
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!
No virus found in this message.Checked by AVG - www.avg.comVersion: 10.0.1375 / Virus Database: 1500/3633 - Release Date: 05/12/11