Best Of
Re: Newbie23
Hi @amehdad I think you meant Left Outer Join instead of Inner Join. Rest the solution looks good.
Another thing, the formula is a fraction, so I think calculating it on the front end might be a better solution.
As the formula might resolve to sum(qty rejected) / sum(qty received) and trying to do it in the ETL might lead to sum of fractions which might be incorrect. Just thinking out loud, pls correct if wrong.
Thanks
JSON Pagination with Response Header
I'm new to working with Domo and the data connectors, but I'm attempting to use the JSON No Code Connector to pull in data from an API. This connector has options for paging and to get the next page or URL from the results. However, this API returns the paging data in the headers. Are there any workarounds for this, or different connectors that offer the functionality to get the next page from the headers?
Re: How do I change my week to Mon - Sun and fix this report?
Since you are sending this every Monday, you can use this beast mode and put it in your filters and then filter to Include.
CASE when `date` >= DATE_SUB(CURRENT_DATE(), INTERVAL 14 day) and `date` < CURRENT_DATE() THEN 'Include' ELSE 'Exclude' END
You would need to change date in my example to the actual date field in your dataset. When filtered to Include, this will only show rows where the date is in the last 14 days and before today.
12k beast modes and counting...
Hi Domo Users!
Wondering if other folks can weigh in on how y'all manage your beast modes being created. I'm the Major Domo for my organization and am finding many cases where the SAME beast mode calculation is being duplicated across datasets with the same name. While clean on the dataset side, this becomes a nightmare in the Beast Mode Manager as I can have up to 50 Beast Modes with the same name. Do you let your users create Beast Modes with free reign or are you putting strict guidelines up for beast mode creation? Would love to know what the best practice is here
Thanks!
Re: Dynamic Chart Height
I agree! Dynamic chart heights could also help with PDP. If you have a table with all rows for Executives, but you needed to limit other users to certain categories, some sort of dynamic chart height could adjust the cards to get rid of white space for users while keeping the executive "all rows" view in tact.

