Patron Ticketing Summary - Across all orders - possible?

Hi all,

We're brand new to Tess, and seem to have stumped our implementation specialist. Hopefully someone else has sorted this out.  

We're migrating from Paciolan, and our patrons became used to our ability to send them an overview of all "active" tickets on their account, after all exchanges have taken place.  Context:  We take exchange requests for known conflicts (or concerts they don't want to see) BEFORE printing season tickets to a) save ticket stock, and b) provide our patrons with tickets for the season that are as final as possible.

An example of this Pac Account Summary is attached.

Is there anything "out of the box" that can provide a listing of all active tickets, with event date/time, seat location, and so on, across ALL orders for any one constituent?  We have multiple "seasons" (ie. Philharmonics, Pops, Compose Your Own, etc) that each concert ticket is bucketed into.  

Any help you can give would be amazing.  I really have tried to self-help.  But there is so much documentation available that despite a search, I can't find a reference to this.  I also know I may be using wrong terminology...Tess has it's own lingo which trips up searches, I'm sure.

Thanks in advance!

~ Emily

2816.Example Patron Summary (Pac)_05 03 19.pdf

  • Sounds like a fun project! Would a patron have multiple orders or would there be one order per summary? 

    The only thing close to that is the order acknowledgements/confirmations for a single order (at least that is all I can think of atm). Have you tried that? If those do not work, I do not know of anything out the box to do this off the top of my head, but it can be created if you have a DB admin on staff. Do you? I would be willing to chat with them for you if it will help. 

    Travis

    UPDATE: Here is a quick example of what is possible in sql. You could easily add address and what not. This query was filter to one patron for the example (Review the where clause). Takes multiple seasons as the parameter. Take note, we are getting multiple orders across multiple seasons in the (3,6,12) sli statuses. Once you have all your information your format the output in visual studio to meet your orgs branding. Again, feel free to reach out and hope this gives you some ideas.

    Quick Code: 

    declare @seasons varchar (4000) = '66,70' /******comma seperated list*****/

    select distinct
    a.customer_no
    ,a.order_no
    ,d.perf_no
    ,d.prod_season_no
    ,fc.description
    ,e.description
    ,d.perf_dt
    ,d.time_slot
    ,f.seats
    ,d.season
    from t_order a
    join T_LINEITEM b on a.order_no = b.order_no
    join T_SUB_LINEITEM c on b.li_seq_no = c.li_seq_no
    join TR_PRICE_TYPE pt on c.price_type = pt.id and pt.price_type_category in (1,2) /*** Subs, Single Tix*/
    join T_PERF d on c.perf_no = d.perf_no
    join T_INVENTORY e on d.perf_no = e.inv_no
    cross apply lft_get_seats(a.order_no,a.customer_no,d.perf_no)f  -- this is a in house function so you would need to join to t_seat or create your own
    join T_FACILITY fc on d.facility_no = fc.facil_no
    join FT_SPLIT_LIST(@seasons,',') ft on ft.Element=d.season
    where a.customer_no = 70865 and c.sli_status in (3,6,12)

    group by
    a.customer_no
    ,a.order_no
    ,d.perf_no
    ,d.prod_season_no
    ,fc.description
    ,e.description
    ,d.perf_dt
    ,d.time_slot
    ,f.seats
    ,d.season

  • To do exactly what you are showing.  I'm thinking you'll need to go to a custom report.  Asking here is a good idea in case someone has already created such a report and is willing to share.  This would save you some time.  Also whoever holds your TASK accounts can look at the repository of shared reports.  You might find something there that is close to what you need.  You might also try to hack something together through Output sets or Tessitura Analytics.  But because it sounds like you are going to do this in a transactional way.  I don't think you will be happy with the many steps that one of these approaches will take.

    My $0.02

  • Would the order export utility report work? It can only be run by one season at a time; and maybe you could do an ad hoc list of the one patron asking for his/her account history???? Test it in Test.