Best Of
Re: PROPER Function in Views
@Sam_Donabedian INITCAP is available in views however it's just not listed in the available functions.
Re: Period Over Period Multi-Value cards zeroing out when user changes the date
@Joe_M I have experienced this as well so have decided to not use the native period over period controls. (Although they are very nice)
@GrantSmith has posted a solution for this that allows for much greater control and flexibility. https://dojo.domo.com/main/discussion/53481/a-more-flexible-way-to-do-period-over-period-comparisons#latest
The only downside is your dataset can become very large.
Good luck.
Jones01
Re: Population calculations in beast mode?
The other option would be to group them, but to group them by each field that you want to be able to filter by... so you would get 1 row for each day and each combination of facility, gender, age, etc. This should reduce the row count a bit.
In your example of 572, you might end up with 20 rows of data that add up to 572, but that would be better than 572 rows.
Re: Population calculations in beast mode?
That's another great idea. This time, I had actually thought of this one 🙂 At least until now, I'd been opting to not go this route, because I'd been unsure which categories I wanted to expose to the eventual dashboard user(s) for filtering. Of course I could just pre-emptively make all of them available to be exposed, but I'd put this option lower on the priority list. In any case, thanks again for the excellent ideas 🙂
datamatt
Re: Period Over Period Multi-Value cards zeroing out when user changes the date
The option to control date ranges in multiple places can be very confusing and result in some strange behavior on a dashboard.
My general rule of thumb is to try to only control the dates in one place. If your end users are comfortable making those changes at the dashboard level, then I would avoid adding any filters to a card that limits the data. You may also need to get creative with some smart text in your card titles to ensure that they align with whatever date grain was selected at the dashboard level. You will also need to be careful when it comes to how you build the multi-value card with the change options. For example, your Month over Month card will want to make sure it is comparing the last two values instead of the first value to the last value.
If you can keep your date controls in one spot, then the cards should all react to whatever is selected there.
Re: Request for Topics
I would like to see more training around some of the newer features. For Example, when you release a new chart type, it should come with a training. Not only a training to help users understand how to build the chart, what options are available in the properties, etc... but also a training about why and when this chart should be used over other options. Why did Domo feel this chart was a benefit to their library?
I would also want training around features. For example, Segments. How do you build segments? How do you use them? But also why would you build segment? What situations are the right time to look into setting up segments as a solution?
In my mind, anytime a new feature or chart type is added, there should be at least one training course to answer these kinds of questions.
Re: Formula for rounding time to nearest minute
I have a question about your example. Wouldn't line 12 get rounded to a different minute then line 13? Line 12 should be rounded to 01:04 while lines 13-15 should be rounded to 01:05.
Otherwise, I was able to use this formula to get to the nearest minute:
"HH:MM"
CONCAT(LPAD(trim(Trailing '.0' from FLOOR(ROUND((TIME_TO_SEC(`Time`) / 60),0)/60)) ,2,0),':',LPAD(trim(trailing '.0' from (MOD(ROUND((TIME_TO_SEC(`Time`) / 60),0),60))),2,0))
I then used a rank and window tile to get a row number for each "HH:MM" value from the above formula. Then I filtered the data for Row=1 to only return one line of data for each HH:MM.
The idea behind the formula is to convert the time value to seconds. You then divide the number of seconds by 60 to get the number of minutes. This will now have a decimal for the fraction of the minute represented by seconds which can be rounded to get to the "nearest" minute.
Re: Formula for rounding time to nearest minute
Would you need to create groupings based on elapsed time then? Something like, if it's within 5 seconds of the initial time then keep it in the same group?
Is it also per ID? What if you had data like this?
Would you expect one group for that time frame? or 2?
Re: Get MySQL on latest version
Another significant addition to later versions is the JSON parser! Probably one of the most underrated functions added that would be especially helpful for most of our source datasets coming from connectors that cant flatten nested objects or more importantly, we bring in the data still nested to keep the row count low on each call.