Dear All,
I have a change over time dashboard on which I have been working which is ALMOST everything I need it to be. The design is to be performance specific, comparing daily and weekly sales of total, subscription, single and comp tickets on a weekly and daily basis with the overall totals across the top. It works fine for all performances for this season up through about December 17th. When I try just turning off the specific performance selected, it loads the entire season data and is just fine there. Weirdly, though, for performances AFTER that date, it just sort of... stops loading correctly and sits there with the three loading dots, and I have let it sit for 3+ minutes, and it still just... sits.
One Performance (September 29th, 2022):
Full Season:
One Performance (January 7th, 2023):
The other odd thing about the January 7th performance is that it was a late add to our season AND it is in one of our smaller venues; the event was not even built until mid September. So it should have far less data to pull than the September 23rd performance both in terms of date span as a whole as well as number of tickets, etc... I highlight this particular one because it has those particular things going for it, but this three dots/not loading seems to hold true for all of our 2023 events if I just try to look at one of them. But again, the whole season seems to be loading just fine, and loads, as far as I can tell, accurate information for all events.
Any thoughts would be appreciated. (Chris Wallingford)
John A. Moskal II
Hi John,
I would probably let it load with a problematic date, then refresh each widget, one at a time, to determine which specific widget(s) are having a problem. You can refresh a single widget from the (i) icon on the widget title bar:
Then, is there anything about any of the formulas in the slow widget(s) that might be impacted differently by the performance date being in 2022 vs 2023? I'm happy to take a quick look at the dashboard if you post it, but may end up referring you to support if I can't see an obvious cuprit.
Nice dashboard btw.
Chris Wallingford,
Thanks for being willing to take a look at this. And if it needs to go support ticket, it is what it is. But yeah, In addition to the widgets across the top, which are really just intended to orient the user as to what is being looked at on this dashboard, the real key elements are the 4 widgets below. The running sales by week/day and the rate of change by week/day graphs. Our management is highly curious in those numbers as that seems to be the relevant aspect in terms of marketing for us. That is what they tell me at least, I am the number guy; I have to provide the data with context, they make the big money decisions.
Anyway, to answer you question, there is nothing in any of the formulas that should have anything whatsoever to do with causing issues for 2022 vs. 2023. I do have an individual widget filter on the four lower widgets restricting them to the date range of 01 April 2022 - 30 June 2023. But that is simply because we have one performance which was originally scheduled for March of 2018 which has been moved now 5 or 6 times (I cannot recall) and will take place (crossing fingers) in spring 2023, and I just assumed that that massive amount of data was not needed for this particular performance (though I am just frankly shocked that we still have ticket buyers from that initial date hanging on here). Anyway, nothing should cause issues in terms of formulas.
I have included 4 dashboard samples. The first is the first screenshot above; the fall 2022 performance which works just fine. The second is the second screenshot; the full season which works just fine. The third is the third screenshot; the performance which fails. And on this one, I DID try to do as you suggest and just wait it out and try to refresh each widget individually, but I waited for 4 full minutes at which point Analytics itself just crashed. No ability to refresh any widgets. So, I took the full season one and simply started applying performance filters directly to the lower 4 widgets. Two of them loaded just fine. Two of them did not. The two that did not were the daily widgets. The fourth sample is the dashboard with the weekly widgets filtered but not the daily widgets. I could get that fourth widget to load just fine as is, but the second I tried to add the performance filter to either of the daily widgets, it stopped working. And again, I cannot think of any reason the full season would load but this performance, which had fewer than 525 total tickets sold all told, would not load.
SalesOverTime - Working Performance.dash
SalesOverTime - Working Season.dash
SalesOverTime - Failed Performance.dash
SalesOverTime - Weekly Widget Filters.dash
You're running into some flavor of this:
Unchecking the Continuous Timeline setting works around the problem. I am not clear on why limiting to some performances and not others, or including the whole season, works with the setting enabled and 14 months of dates in scope. Due to this issue however, when the Continuous Timeline setting results in this behavior, we recommend filtering to fewer dates, or using a higher level date grouping (like your weeks widgets), or disabling the setting.
I wish I had better news, but I also could not reproduce this on the later Sisense version of my v16 Tessitura instance.
I wondered if that was the case, but it just seems VERY weird in what is working versus what is failing.
If you are saying that it all seems to be working correctly in Version 16, that is certainly nice to hear, but yeah I suppose we will just deal with it for now.