Hi all,
We had an unfortunate incident last year where a performance had to be rescheduled, and at the time we announced this we did not have a confirmed date. The original date of the performance passed us by and we did not update the performance date in Tessitura to some date in the future.
We offered patrons the option of holding on to their ticket or they could get an exchange.
Because we didn't change the performance date, I can see that constituents how have ticket history rows relating to the performance - as would be expected. However, this obviously doesn't get updated for those who received a refund after the performance date, which means the ticket history tab is wrong.
Has anyone had any experience in this before? Would there be any problem with me just deleting the rows in the ticket history table relating to the affected constituents and this performance? There are only a few and it's easy to identify them.
Cheers
David Geoffrey Hall
Were the refunds done in Tessitura or were they done externally?
If they were done in Tessitura (meaning they are no longer seated the performance), you should be able to run the procedure that updates your Ticket History manually with parameters that would capture that past performance.
Hi Beth
Thanks for your reply. I just discovered our nightly lp_update_tkt_hist was skipping past performances. All fixed now.
dgh