Best Of
Re: why is greater than filter not working for date.....????
I believe there is a glitch right now with the filter tiles. The way I have gotten around it is to use the formula function in the filter and then wrap the date function around each item so that it sees them both as dates. Like this:
DATE(`mydatefield`) < DATE('6/30/2021')
Re: Beast Mode for Sum Function
@ozarkram - I think that @GrantSmith 's approach is a better option here. He has included safeguards for any null values. If you choose @MichelleH's solution you will get a null value if any of the three fields are null.
Re: Using ETL formula for finding between dates
You can do some simple date manipulation to get the Monday of the current week with a Formula Tile
`Date` - INTERVAL (CASE WHEN DAYOFWEEK(`Date`) = 1 THEN 6 ELSE (DAYOFWEEK(`Date`) - 2) END) DAY
DAYOFWEEK returns a number between 1 (Sunday) and 7 (Saturday).
The CASE statement is checking if it's a Sunday to subtract 6 days instead of 1.
-2 is to reduce the days to subtract to get to Monday. For example Tuesday (3) we need to subtract only 1 day instead of 3 days.
You can then tie it all together with a CONCAT function and a DATE_FORMAT:
CONCAT('Week of ', DATE_FORMAT(`Date` - INTERVAL (CASE WHEN DAYOFWEEK(`Date`) = 1 THEN 6 ELSE (DAYOFWEEK(`Date`) - 2) END) DAY, '%m/%d'))
Re: why is greater than filter not working for date.....????
@NathanDorsch , if your first filter is removing all data prior to 6/30/22, then you might not have any data greater than 6/30/21 available after that first filter is applied.
Re: coalescing data in a table
Whenever you want to do an aggregation you need to put your function on the outside of your case when statement. If you do case when 'x' then max(date), the beast mode just does the calculation for each individual line, so it will just take the max date of each row in your dataset. If you instead do MAX(case when 'x' then 'date') then the beast mode will treat that as an aggregation and will look for the MAX date in your table groupings.
Re: How do beastmodes handle filter context?
The key is that your SUM(Implementing) is a multiple of your Implementing column. Whenever you have one column that is not an aggregate and another that is an aggregate, Domo will group the non-aggregated column. So for example, in your data it looks like there is one row with 13 hours, two rows with 42 hours, 3 rows with 24 hours, etc. It groups your data by that column and then gives you the sum of that grouping. When you add in the distinct ID's, it can only group by individual rows and so you get SUM(Implementing) and Implementing being the same.
Re: Removing the borders between domo cards
Currently Domo doesn't have a way to remove the borders. I'd recommend adding it an idea in the idea exchange for the product team to possibly review and have other users vote on.
Re: How do beastmodes handle filter context?
@NateBI Aggregate functions like SUM() and COUNT(DISTINCT) use multiple rows to return a single value. The way that the data is grouped or filtered affects which rows are included in the aggregate. When the data is grouped or filtered by a dimension, then the aggregate value for each category will be evaluated using only rows that have the same value for that dimension.
If your beast modes are not behaving in the way you expect, I recommend first reviewing the rows that are returned when you drill into the card to better understand which rows are being included in the calculation. Then if you still have questions, I second @RobSomers that it would be helpful to post some examples in this thread so we can help come up with a solution.
Re: Calculating Summary Level Average of a Calculated Field
Hi @RanjitR try adding a second beast mode for the summary number that divides the average for the whole period over the number of weeks:
((SUM(`CY_TRANSACTION`) / COUNT(DISTINCT `STORE_ID`))) / COUNT(DISTINCT `YEAR_PERIOD_WEEK`)
Re: Uploading daily reports csv in box
Have you looked into the dataset via e-mail connector for this process? Using this connector would eliminate the need for the Box connector and you can use your Outlook rule to forward and append or replace the dataset. You can read more about it here:
https://domohelp.domo.com/hc/en-us/articles/360042931954-DataSet-via-Email-Connector




