I was trying to figure out if I could have a callout of sales metrics for the next show in the season by using some sort of widget filter and ranking. I'm coming up short, however. I tried ranking with top 1 of Performance Date:
That seems to work in some cases but not in others, so I'm not completely comfortable with it. Also, I'm pretty sure that if there are two shows on the same day it will choose one arbitrarily.
It makes me wonder if there might not be a way to include in Analytics dates a field that is just the raw number so that you can do direct date comparisons.
Okay, I think one problem with this will happen when that performance passes. I need another filter to filter out past dates, but you can only have one filter on each field, so if I try to add something like that it deletes this filter.
Hi Gawain,
Here's an example with Production Season Opening Date. It should work for Performance Date if that's your preference.
MIN(DDIFF([Days in Production Season Opening Date],NOW([Days in Production Season Opening Date])))
We could use that to grab the smallest positive result as our filter. That's the BOTTOM 1 by a conditional version of that formula that returns NULL when the date is in the past.
IF (MIN(ddiff([Days in Production Season Opening Date],NOW([Days in Production Season Opening Date]))) < 0, NULL, MIN(ddiff([Days in Production Season Opening Date],NOW([Days in Production Season Opening Date]))))
Whether Production Season Opening Date or Performance Date, it's only limited by that date as an attribute of all the data that is then in scope for the dashboard. So if you use Performance Date and there are 2 events on that date, they'll both be included.
Interesting. Is "Days in Date" basically "Days since Epoch" or whatever the term of art is?
Date in this case is the field name. If the field were called Performance Date, it would read as Days in Performance Date. That it's Days in... is the grain at which we're looking at the date. It can be changed to Weeks in Date or Quarters in Date or Years in Date.
But it's basically an integer, right? I'm wondering if the integer is based on, say, January 1st of the year in question, in which case this would be problematic. Or is it something else?
The Date field is a "date" data type, not an integer.