• Replies 14 replies
  • Subscribers 698 subscribers
  • Views 122 views
  • Users 0 members are here
Options
Related

Pricing Rules vs Discounts - Attendance Tracking Nightmare!

Chelsea Marti
$organization

I am still dealing with issues from our summer discounts from 6 months ago! 

Here is the issue: 

To make things easy for our Front Desk this year, instead of doing it all as a Promo/Source Code (like the year before which gave inaccurate numbers because the Front Desk forgot to switch the source code between orders) I created a Discount for the in-person sales and then kept the Promo/Source code for online sales. 

This worked great in built out and for our front end; however, because pricing rules/sources and discounts are two completely different things, reporting on them has been a nightmare. I have 2 different widgets set up; one has the discounts, the second has pricing rules. The problem is the Total Attendance is the same for both, but the breakout is different and we don't know why. I don't know if I built the widgets wrong, or if its because I'm trying to get Tessitura to do something it simply won't. 

What our org needs: 
Total number of attendance by Ticket Type for ALL discounts (discounts and pricing rules combined); separated by discount. 

So basically I want to combine the two widgets into one clean widget. 

Attached is the dashboard file (ignore the comp reason widget, that is completely correct and what we need).

 CLM71223-CompReason&Discounts.dash

Parents
  • $organization

    Hi Chelsea,

    Your best bet may be to look into a simple customization to include a field for your organization that would be populated with the Pricing Rule or the Discount Type. Then with this single field, all CT Summer Free would be grouped together in a single result.

    Alternatively you could look at creating a value that includes the matching Discount Type for the given Pricing Rule. The issue here is that we're limited to 10 distinct filters on any given field within a formula. So this would only work for up to 10 Pricing Rule + Discount Type combinations. To set it up, with a filter on Discount Type set to include only (none), and with Pricing Rules on Rows, we could use a value that takes the [Total Ticket Count] for the Pricing Rule, plus a CASE statement that has an entry for each pricing rule and adds in the appropriate discount type ticket count. E.g.

    [Total Ticket Count] + CASE
    WHEN MAX ( [Pricing Rule ID] ) = ( MAX ( [Pricing Rule ID] ) , [Pricing Rule = CT_Summer Free] ) 
       THEN ( [Total Ticket Count] , [Discount Type = CT_Summer Free] , [Pricing Rule = (none)] )
    WHEN MAX ( [Pricing Rule ID] ) = ( MAX ( [Pricing Rule ID] ) , [Pricing Rule = Next Pricing Rule] )
       THEN ( [Total Ticket Count] , [Discount Type = Next Discount Type] , [Pricing Rule = (none)] )
    END

    If this were not a Pivot widget, but a Bar or Column, then the bucketing like others have suggested could work (Jo's example), but in a Pivot these will render as columns rather than as rows.

    A custom field (just open a support ticket to explore it) seems like your easiest and most flexible way forward.

Reply
  • $organization

    Hi Chelsea,

    Your best bet may be to look into a simple customization to include a field for your organization that would be populated with the Pricing Rule or the Discount Type. Then with this single field, all CT Summer Free would be grouped together in a single result.

    Alternatively you could look at creating a value that includes the matching Discount Type for the given Pricing Rule. The issue here is that we're limited to 10 distinct filters on any given field within a formula. So this would only work for up to 10 Pricing Rule + Discount Type combinations. To set it up, with a filter on Discount Type set to include only (none), and with Pricing Rules on Rows, we could use a value that takes the [Total Ticket Count] for the Pricing Rule, plus a CASE statement that has an entry for each pricing rule and adds in the appropriate discount type ticket count. E.g.

    [Total Ticket Count] + CASE
    WHEN MAX ( [Pricing Rule ID] ) = ( MAX ( [Pricing Rule ID] ) , [Pricing Rule = CT_Summer Free] ) 
       THEN ( [Total Ticket Count] , [Discount Type = CT_Summer Free] , [Pricing Rule = (none)] )
    WHEN MAX ( [Pricing Rule ID] ) = ( MAX ( [Pricing Rule ID] ) , [Pricing Rule = Next Pricing Rule] )
       THEN ( [Total Ticket Count] , [Discount Type = Next Discount Type] , [Pricing Rule = (none)] )
    END

    If this were not a Pivot widget, but a Bar or Column, then the bucketing like others have suggested could work (Jo's example), but in a Pivot these will render as columns rather than as rows.

    A custom field (just open a support ticket to explore it) seems like your easiest and most flexible way forward.

Children
No Data