Hey everyone - I'm relatively new to Tessitura, and we're still on Version 10, but I've been tasked with exporting the entire order history for one of our constituents. I've searched and searched on the forums, tried to go through the reports, but I'm still unable to figure out how to do this. Would it be an output set? Has anyone else been able to successfully do this?
Thanks so much,
David SluderAtlanta Symphony Orchestra
Hi David,
What about the canned Tess Report called the Order Export Utility, which can optionally be run on a list? If you created a list of of the singular constituent who you needed this info on, and ran the utility on that list, perhaps this would work for you with all other parameters set broadly - all season, all price types, broad Performance and Order Date range, etc.
One thing to note is that I believe this utility only pulls out of Orders and LineItems, so if you have in the past had imports (as we do) that are only in Ticket History and not in your Orders screen, this will not grab those.
Good luck!
Frannie
David - depending on what you need you also might want to look at building an output set. Then you can run that output set against a list of one. It should export one line per ticket history line.
Let me know if that doesn't make sense!
Heather
You would need to be very careful doing this with an output set as you could get an exponential set of rows combining each combination of fields from each entry in the ticket history. There really aren’t any standard elements that will give output one complete row for each order or ticket history entry. You would need to add an element that combines multiple fields of data in a single element. You can find instructions on how to do this in Part 3 of the Output Builder T-Cast.
Kevin Sheehan
Senior Technical Writer & Consultant
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
Thanks for the clarification caveat Kevin!
It's definitely only an easy possibility if it is one of those 'if you need just a show name' or 'just a seat location' things. Sometimes in my organization when people ask for a dump of history they literally are just asking for all the shows the person has come to, and nothing more than that, which is why I mentioned output sets. But yes, do be careful if you want multiple fields of data! It will at least be easy to see what you are outputting with only one person in a list, which is always a good thing when dealing with output sets.
- Heather