JedP Domo Employee

There sure is, here is the link: https://embed.domo.com/embed/pages/mO1RR

So cool!!

Hello @abarrie23 , I think i see the issue here, it looks like you are mixing your aggregations in your case statement. The THEN result appears to just be a non aggregated column, while the ELSE results in a Window function aggregation. When you mix aggregation results and non aggregation results you end up with multiple…

Good call out @shreeb , that example does not call out holidays. You can always add in other conditions in the case statement to include the specific holidays. The down side of this method is that you would need to update the code each year with the new holidays. Another really common method is to place the date & holiday…

Hi @shreeb , You can add a case statement to narrow the data used in the beast mode code. For example, if you want to see Monday - Friday as the 5 days, then you could modify your code like this: SUM(SUM(CASE WHEN WEEKDAY(ProductionScheduleDate) BETWEEN 2 AND 6 THEN Orders END) FIXED(BY AssignedTo, ProductionScheduleDate -…

Hello @mcruz24 , Yes, you can use variables to create weighted options and its usually the go to option to ensure your data is dynamically calculating the values. I have a few demo pages that use variables you could review for some ideas and sample codes. Take a look and let me know if you have any questions. Variables -…

Hi @david_cunningham , This is likely possible with some type of tool tip use and a windows function, let me test out a few examples and if i can get one working ill post the results here.

Hi @SimonKing , I was able to find Googles Scope documentation that provides the scopes and the actions that the scope can preform. It looks like a pretty big list, so you might want to do a quick search for "SDK" to find the SDK specific scopes. Google Scope Documentation:…

Hi @TejalGovila , Here is a good example page of a few types of variables used to show different time slices. Example Period over period variable page: https://embed.domo.com/embed/pages/8qNll

Hello @Cara , Great question, this is due to the aggregation rollup on the card and the dimension grouping used on the card. The **** error indicates that the grouping in your pivot table doesnt match the grouping in another part of your visual, in this case its your Beast Mode code. A common way this happens is when you…