Hello,
We recently had an issue where someone mistakenly refunded a pair of tickets for an event that was a year old (it was similar to a current event). They loaded the old order, so MOS dates did not affect it.
Is there a control we can use to ensure a performance can no longer be transacted upon?
Nick,
Do you utilize the 'off-sale' functionality of performances? By that I mean the 'on-sale' check box on the performance itself. Unchecking that SHOULD restrict a performance from being able to be transacted upon. Note that that is distinct from the 'status' of a performance which does nothing other than notes it for your reference. If you are looking in the database, the correct column would be the avail_sale_ind column.
If this WAS part of a package, and the package itself and one or more performances ARE still on sale, weird things can happen there, so if that is what happened, you might want to look into that. Even when using this off sale functionality returns can still sometimes happen. I have been involved in more than one thread on the forums about that, but it has been a while, and I am not sure about the resolution of that.
Elsewise, if you ARE using that functionality and this somehow STILL happened, I would open up a ticket.
Lastly, if someone was doing a transaction on an old order with that performance for a different, active performance, because of the way Tessitura saves payments, weird things can happen when you make payments to already existing orders, especially if returns are involved, even if you did not touch a particular performance. But from what you said it sounds like this would not be the case here.
Let me know if that helps.
John