Best Of
Re: Pivot Table Total Column Position
THIS! This feature would improve the user experience extensively as scrolling would get minimized in case of pivot table with high number of Value columns.
Manthan
Re: Calculated line on Bar Chart not the same as Summary Average
Without seeing each of your bar values, I believe the chart line is taking an average of each percentage/bar in your chart, but the summary number is taking the percentage across the entire dataset.
Re: Sum x for each unique y
@Charlie Bantoft here is more detail on how to do Fixed Functions. I find fixed functions allow for more flexibility then an ETL, especially if you want to do filtering on other fields.
Ashleigh
Re: Column Total Greater than Sum of ROWS
@jtrollinger Total rows calculate based off of values in the source dataset, not the aggregated values in the table rows. In this case it means that there were 47 unique values in the SalesOrderNo field, some which have records for multiple Assigned Plumbers.
Re: Column Total Greater than Sum of ROWS
Likely, you have multiple records for the same SalesOrderNo value so when it's doing it in aggregate it's doing the distinct count across all superintendents instead of adding each individual distinct count per individual superintendent.
Re: Multiple cases in CASE WHEN
Should be:
CASE WHEN `Type` IS NULL THEN 'Daily' WHEN `Type Sourced Daily` IS NULL THEN 'Monthly' ELSE 'Mutual' END
You need to drop the extra "ELSE" and use single quotes ' ' instead of double quotes " "
Re: Column is Adding rather than giving Average
Because your aggregation is within your case statement, it's getting treated differently.
Try this instead:
COUNT(DISTINCT CASE WHEN HdrParentItemCode = 'ZPUNCH' AND JT158_WTParent = 'Y' THEN sonum_wtnumber END) / COUNT(DISTINCT CASE WHEN JT158_WTParent = 'Y' THEN SalesOrderNo END)
Re: Can I show 2 values as a stacked bar and other values as single bars?
An alternative would be to incorporate a line to represent your goal that way you don't need as many bars. I do something similar for the same concept. I made an example in the community Domo instance that looks like this.
I think having either the prior year or the goal as the line would make sense to the user and then you only have 1 bar to compare you stacked bar to.
Ashleigh
Re: How do I construct my desired query?
The issue is that your metadata variable is undefined and you need to handle the Promise. I'd try to do something like:
domo.get(metadataQuery, {format: 'array-of-arrays' }).then(function proces_metadata(metadata) {
fields1 = metadata.columns
…
domo.get(query1).then(…)
}
)
Re: Filter NULL values within Analyzer
Domo can’t recognize a filter to show null records. The easiest thing to do is create a new field with a beastmode that is something like this:
CASE WHEN Brand IS NOT NULL THEN Brand ELSE ‘null’ END
Null values will then be replaced with the word Null and you can apply the filter as you would normally.
you could also use IFNULL() or COALESCE() functions to accomplish the same thing.