Hi all
We have had a problem with fees doubling where events in 2 different seasons are sold together in an order (we have a flat-rate transaction fee). At the moment Ticket Office staff manually remove the second fee, but it does occasionally happen online as well. We have not had any custom code written to stop this (yet).
I remember seeing this on the enhancement lists over the last few years but I'm not sure if a solution came with any of the upgrades.
Does anyone happen to know anything about this?
Thanks!
Katie.
Replying to this thread on behalf of the Tessitura Network:
Modification of any standard data objects including tables, views, stored procedures, or indexes that are not designated explicitly for customization (i.e. are designated "localized" LT, LRP, LP...) is prohibited, is in violation of the Tessitura member and support agreement.
Gregg Stickney
Director of Support
Tessitura Network
Hi Gregg
When can we expect this enhancement to be in place or actually this defect to be resolved as we really need this functioning properly - order level fees should be at an order level. The general feeling is that a lot of licensees need this - it still comes up as a topic about every year here in the UK but no one complains anymore as they don't think anyone is listening.
Thank you
Hi Roberta. My apologies for not responding sooner as I was out of the office for the US holiday. I referred this thread over to our Development team as they would be best to update as to any plans on this front. A representative will reply as soon as possible. Thank you.
Roberta, while we certainly see many use cases where multiple order level fees should be applied to an order we do understand the problem that the behavior around multiple order level fees associated with different fiscal years qualifying for a single order poses for some members. While we cannot say at this point whether a change will be made to address this scenario, Development is investigating a way to mark an order level fee as superseding all other order level fees that do not have this indicator. Any feedback on that approach as a possible solution here? (We can't yet commit to a time frame, but certainly welcome your comments!)
Bob,
We have also had similar issues with fees in the past. I am wondering if there might not be a way to have something like pricing rules but for fees where the fee acts as the price type, for example. Just an idea that might help to both A) solve a situation like this and B) allow a fair bit of additional flexibility with fees in general.
John
Thanks Bob, we also would love something like this. Weve lost revenue and annoyed customers/accountants having to switch fiscal year fees by hand.
On a super basic level a T_default to apply only one order level fee with Max fiscal year.
Although as John says more fee flexibility would be very welcome.
We would definitely appreciate this kind of indicator in the Fees Setup, Bob, as this is a regularly occurring issue for us.
I am pleased to report that in Tessitura v16.0, an enhancement will be made to Fee Rules functionality that will introduce a new Suppression filter that will allow an Order Level fee to suppress any number of other Order Level fees. For example, Order Level Fee-2020 is associated to Fiscal Year 2020 and Order Level Fee-2021 is associated to Fiscal Year 2021. You would be able to set up Fee-2021 to suppress Fee-2020 so that only Fee-2021 would be applied to an order that includes Performances or Packages for both Fiscal Years 2021 and 2020.
Great news!
Very happy to hear this!