-
Beast Mode Examples
Sorry in advance if this is already a thing but I haven't been able to find it. As a new user to SQL, I understand the very basics. Beast mode provides a really simple and easy way to apply some of what I know and quickly help with new calculations. My issue, and where the idea comes in, is that I don't know where to go to…
-
Beast Mode URL via Governance Data
As a Domo Admin, I need a way to use governance data to build a URL that links to a beast mode so that anyone using the card with the link can quickly access the screen to edit the beast mode. Unfortunately, the Beast Mode ID in the URL doesn't match the calculation ID in the governance reports. If I'm writing acceptance…
-
Configure Instance to Share Beast Modes to Dataset by Default
We would like the ability to set the check box "save as calculation on datatset" to 'checked' by default so that when users are creating a new beast mode it is automatically saved to the dataset. This would save us days of governance and administration work having to clean up multiple beast modes with the same name on a…
-
Lock a Variable
It would bring a lot of peace of mind if we could lock variables in the similar manner that we can lock beast modes in the beast mode manager.
-
Sumo Card Add All Fields - No Beast Modes
It would be helpful if we had the option when creating or editing a beast mode to add all dataset fields excluding the beast modes. If beast modes have an aggregation in them or if they have invalid syntax that can break a sumo card or cause unwanted grouping. We use Sumo cards who quick data analysis and it is painful to…
-
More traceability with variables
Knowing that this was just launched and probably has a lot more coming, I think it is key to increase traceability of variables. Let me elaborate: once you set a variable, you need to create a BeastMode Calculated field to actionize this variable through a CASE WHEN. However, this first CASE WHEN is then used as input in…
-
Beast Mode Manager Switch to New Beast Mode
It would be helpful if we were able to switch all cards and reports that use a beast mode to a new beast mode. There are several instances where a beast mode was not saved to the dataset but rather to a card and then it was saved as numerous times so when we go to the beast mode manager we have "Days Late to RD" 15 -20 on…
-
Duplicate Beast Mode Warning
It'd be cool if when making a beast mode Domo could warn you that a similar/exact beast mode already exists. If I'm doing a new one that's Count(Distinct SalesOrders) it could suggest that a duplicate beast mode already exists. Or possibly a Beast Mode manager feature.
-
FIXED Function - Static Filters
FILTER ALLOW/DENY is the most useful piece of FIXED for me. What would juice up its usefulness to the next level is an ability to use static filters in the function. For example - SUM(SUM(`totalSales`) FIXED (FILTER `Client`='ABC Company')) Beyond simply allowing or denying field filters to affect the calculation, you…
-
Field list in Beast Mode Editor
When opening the beast mode editor, the fields listed in dataset fields are not in alphabetical order. However, the fields are in alphabetical order in the dimensions and measures section of the card analyzer. It would be great if the fields in the beast mode editor were in alphabetical order, so that they are consistent…