Is there a way to make "order weeks since onsale" dynamic?

Those data points do have the 'custom' tab for them, so you could move beyond the default array of options. How would you describe your ideal setup for such a widget/dashboard? Maybe we can work backward from there.

Hey Nathanael -- thanks for the quick reply. 


Ideally, I'd like to be able to use the field dynamically to compare current FY package metrics to previous FY package metrics at the same point since packages went on sale. E.G. how date fields can use the relational filter of "timeframe" to compare specific segments of time YoY. 

I think we'd want a field + filter combo that does two things
1. starts counting days or weeks at a specific start point in time YoY -- e.g when packages go on sale
2. dynamically increases the inclusion of the field to count more days/weeks as we move forward in time from that specific start point.  

If the Performance setup is consistent, I know you can use 'Order Days Prior to Performance' as a metric- I've used that in the past.

You also can use custom formulas to create "AND" conditions within those metrics. For instance, I've used "Show me dates from 1.1.24 - 12.31.24 that are ALSO WITHIN the last 365 dates, offset 1". In other words "Show me all the dates from Jan 1st of this year, that are also up through yesterday".

This helps me keep a dynamic "This year, up through yesterday" filter going for Performance Dates.

My thought is that you could set up something like that, to say "For X and Y Perf Seasons (a filter on the dashboard), show me all sales that happened between 2 and 10 weeks out from the performance (a filter using 'prior' metrics)".

I'm curious if others have found a useful way to get year-over-year compares using these measures as well. A problem we're facing here is getting a reliable count for something like "how many subscriptions have we sold up until today's relative point in the campaign?"

I can use "order days since onsale" as a dashboard level filter, for example. But I then need to manually adjust this count up by one every single day to capture the next days' worth of sales on previous seasons. Correct me if I'm off-base here, Erik, but I think what you're asking is whether or not this manual process (adjusting the static count for "how many days has it been since onsale") can be made into a relative field. I'd be interested in that as well if anyone knows how this might be done!

We use running sum sales curves from onsale date, and overlay the different seasons on there to track how we're doing on various things like price type group in the way you're asking (how well are we doing up to this point, compared with same point in previous campaigns), and the existing season's sales curve is just shorter (as it hasn't yet run full course yet).  I may be missing what you're after here, but wondering if that could help?  Our situation could be simpler than others though as we tend to go on sale with one main annual season at virtually the same time every year.

RSUM([Total Ticket Paid Count])

Thanks Melanie! 

Yeah, I have a sales curve like that as well, but for sending the data out to non-Tess users, I also like having a few pivots to show the numbers of where we're at as of this same point in the campaign last year:

This works fine, but in order to keep it up to date, I need to adjust the filter daily (or weekly) to show the current number of days that have passed since the onsale.

Showing some old numbers here, but this widget is showing a running sum of orders, renewing orders (filtered by my list of renewable subs), and the % renewed - the dashboard filter on the right is what I need to update daily to increase the relative order date - if there's a way for me to not have to update that daily, that would be grand!

I do always like seeing other orgs using the same types of sales curves/widgets as I do!

Hi John and Erik,

First could we rule out that the Fiscal Year to Date Flag won't address this issue? That the "onsale" date from which you're measuring isn't also the start of your fiscal year. If it is also the start of your fiscal year, then try filtering your ORDER DATE Fiscal Year to Date Flag to Y and see if that works.

We also could try something like this... using John's Pivot widget as my target... a formula value flag that returns a 1 if the Order Date is on a Days from OnSale that is <= the Max Days from OnSale for the current Season Fiscal Year. 

IF (
   [Max Order Weeks from On-sale] <=
      ([Max Order Weeks from On-sale],[Season Fiscal Year],ALL([Days in Date]))
   ,1
   ,NULL
)

Then filter the value on Value = 1. Then disable the value from being displayed in the widget output. Ignore that I happen to have sales in my data in October of 2024 .

Amazing! This looks like exactly what I was looking for - will try it out and see how it goes

I compare subs season sales YOY but often get asked about day to day micro movements (the data behind the pretty trend line graphs) - not sure if this helps but I created a mini dynamic pivot showing last seven days of stats according to which onsale date we're on in the current season.

I had to go back through the ticketing set-up for all past shows I was tracking and made sure that the MOS dates and default start dates aligned with the actual onsale dates so my YOY tracking would be more accurate.

In a Pivot of RSUM and SUM metrics - I made...Order days from On-sale my ROW and season my COLUMN. NB - We also exclude some layers in our set up but it should be easy enough to tweak the formulas to include / exclude what you need for your set up.

I then applied a custom filter to the row to look for the last 7 days worth of metrics - when compared to previous seasons - it's as dynamic as I could make it but it seems to do the trick.

• Hit the filter icon
• Select Ranking | Set it to Top 7
• Click into the formula bar (below the word Top)\
• Use a bucket formula in tandem with the top 7 ranking to use this years season as a filter i.e
  
  (MAX([Max Order Days from On-sale]) ,[Season1] ) - in this example above I edited the filter on Season1 to our 2024 season.
  
  I've attached the dash file in case I am making zero sense right now. I've also used some Sisense Java coding found on a forum to make the pivot shading a little easier to read.

https://drive.google.com/file/d/155Ykab8QdyJXDzMzVZxSHK8VMpjXZ4zC/view?usp=sharing