Best way to extract season ticket information for mail merge to constituents

Hey everyone,

Thanks for any help in advance. Our organization is about to mail season letters to all of our 2019 subscribers. We need the basics for this letter - their name, tess and order #, as well as their exact dates and the seats relevant to that date. We have reserved packages with standard sets of production dates, but this information becomes harder to extract with our flex packages, when the patron's dates are all over the place and the seating inconsistent.

I have yet to locate a report that easily gives us this information that, when exported to a CSV or excel sheet, is easily transferable to a mail merged word document. Does anyone have any recommendations on this? 

Thank you!

(We are still in v12.5.1 by the way)

  • Former Member
    Former Member $organization

    Hi Tyler,

    We're in a similar situation (we only sell flex packages) and our process isn't easy, but it works. Most of our season letters don't have performance information, we just print the tickets and let them get it from there. For those we can't print tickets for the process is multi-step, but it gets us there.  I started from TP_ORDER_ACK, added a function to get seat locations, and flattened the output a little bit. Then I run my modified procedure in SSMS and put the data in Excel, where I can mail merge. However, since there's a row for each performance, the mail merge template has a good number of If statements. I inherited it, but would be happy to share if you are interested in trying to decode it for your own use.

    Another option would be to create a new Confirmation Format in Infomaker and then run the Order Confirmation report. I don't think that has seat information, so there'd be more editing there as well.

    Perhaps someone else will respond with a better solution I could take advantage of too!

    Dorothy

  • Former Member
    Former Member $organization

    Ticketing Processing > Order Export

    aka The God Report

    It will require data manipulation and confidence while using Excel, but this report can give you that which you desire without requiring any custom reporting.

  • This is really late, but in case anyone comes here looking for it, get the Package Location output field added to your Output options. This is a data field that shows package locations as a string, just like in your package history tab. It still takes some manipulation if you like your data to be Seat(s) 1 - 5, but it is much better than anything else I have found. I have a help tech at the last conference add it to my company's database, so maybe just reaching out to the help line?

    One problem I have so far is that it doesn't always work with unpaid seated rollover data. Sometimes I get results back and sometimes I don't - haven't figured out what the difference is between my orgs other than one is super package (sub packages pull back the data I need) and one is a fixed package (doesn't pull back the data I need).