Best Of
Re: Brick with Ten Datasets Question
There are two ways to interact with the Domo APIs, the first being a more object-oriented approach and the latter being url based approach.
This documentation lists out the different types of aggregation you can use in your query request:
It's not much but should highlight the possibilities for aggregation.
Re: Group By Filter for Dashboards
You can change the dates based on presets… not sure if you can change the graph by options with a filter card though. Maybe a feature request?
Re: Help with the SUM function, I get "An issue has occurred during processing"
It seems like you should be able to just use
COUNT(DISTINCT `idcontent`)
Then you can set that value as a filter and select >5 or >100, whatever you want to filter for. Then, just include UserId and Name in the table.
Re: Help with the SUM function, I get "An issue has occurred during processing"
You can't do an aggregate on aggregate without using an OVER clause (window function) or the new fixed functions. Here is the KB article on fixed functions.
Another option is to only have this in your beast mode:
CASE WHEN (COUNT(UserId) > 100) THEN 1 ELSE 0 END
Then once your drag into the field you want on your card, choose the aggregation type of sum.
Re: Display Values used to calculate Summary Value
You can show multiple summary numbers in the summary number box by creating a beast mode to show those numbers. Here's one previous post that talks about how to construct the beast mode.
It's a pretty convoluted beast mode. I have started to move away from this and create another card that would sit right above the other card and use the multi-value gauge card to display the summary information. This works well if you intending your users to look at an entire dashboard to view the information. If you don't have a dashboard page constructed, and are just having a single standalone card, this might not work for you. Here's what it can look like.
Re: Average Time between Orders
If you're looking to do this per customer you can utilize a Rank & Window tile and use the LAG function to get the prior record's value. You'll want to partition based on the customer ID. Then you can use a formula tile to calculate the difference between you current version and the lag version. Then put that into a Group By tile and calculate the average for each customer
Re: Is there a reason why you cannot change the legend labels in a Period over Period chart type?
@jakebutterfield Domo's PoP charts are generally pretty rigid as far a customization goes, unfortunately. What have you tried in the bar + line charts?
Re: Is there a reason why you cannot change the legend labels in a Period over Period chart type?
Looks like the series that you were using is Year. I would try creating a calculated field. Assuming you don't have any future dates in your data you could do something like this:
CASE
WHEN
DATE_SUB(DATE_SUB(CURDATE(), INTERVAL 12 MONTH), INTERVAL DAYOFMONTH(CURDATE())-1)
>DateField
THEN 'Current'
WHEN
DATE_SUB(DATE_SUB(CURDATE(), INTERVAL 24 MONTH), INTERVAL DAYOFMONTH(CURDATE())-1)
>DateField
THEN 'Previous'
END
You could then place this in your filter and select 'Current' and 'Previous'. Then use this field as your series as well. You can change the "Current" or "Previous" in the formula to whatever you want the label to say
Re: Is there a way to count all views of a card, including dashboard views?
Page views and Card views are separate from each other in the activity log. You'd need to utilize an ETL to join the governance dataset for cards and pages to the page ID in the activity log and then count each of those page views as a card view in the resulting dataset.