Doubling Fees

Hi Katie

We find this is a problem when selling for 2 seasons too. The Box Office have to remember to delete the 2nd fee.

We too would be grateful to hear any suggestions!

Dawn

Hi Katie,

Are all of the seasons that are on sale in the same fiscal year?  If so, then in the Ticketing Season dropdown in the Fees Maintenance tab, we use  - (all in fyear).

Duane

Hi, everyone -

We've got the same thing right now, too - again, because they span the financial year. It would be great if anyone had any creative ideas around it!

C.//
X. 

Has there been a solution or enhancement in the past couple of years to resolve this issue, of double charging order fees when a shopping cart contains product from two different fiscal years?  This is the first year we have productions on sale across two fiscal years, and is now an issue for us.

Thanks,

Duane

We also have this problem. With website orders the operator can't remove the extra fee so we have worked around this by adding the following code to the WP_ADD_FEES_TO_CARD SP after the execute dbo.TP_CALC_FEES call.

Obviously any changes to Tessitura SP's must be done with caution and need to be re-applied after any system version updates.

Hopefully the enhancement will be implemented in a release soon.

SQL Code below:

--DH TEMP FIX: REMOVE MULTIPLE POSTAGE FEES

delete @fees

--select *

from @fees tf

join t_fee f on f.fee_no = tf.fee_no

where f.category = 0 --category 0 = Online Postage Fee

and f.fee_no = 11 --only the standard postage fee

and tf.id NOT IN(select top 1 tf.id

from @fees tf

join t_fee f on f.fee_no = tf.fee_no

where f.category = 0 --category 0 = Online Postage Fee

and f.fee_no = 11 --only the standard postage fee

order by f.fiscal_year desc

)

Dara

Well its been 9 years and fees at an order level are still doubling when performances purchased in an order cross financial years.  Since changing the web site would costs us £££, we chose to add your modification to WP_ADD_FEES_TO_CARD.  We are testing at the moment and so far it is working!  Thank you!

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  

No problem Roberta Harrill,

Glad it works. As Gregg mentioned it would be better if this was party of the core application.

I did log an enhancement request for this 9 years ago, but it will need others to do the same for it to be an feature worth implementing in the core product. 

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.