Best Of
Re: How do I bucket (group) different Levels in Beast Mode?
Create a beastmode. Replace 'FIELD' with the column that contains the values you're looking at.
CASE
WHEN 'FIELD' IN ('Level 02','Level 03','Level 04','Level 05','Level 06','Level 07') THEN 'Level 02 - Level 07'
WHEN 'FIELD' IN ('Level 08','Level 09','Level 10','Level 11') THEN 'Level 08 - Level 11'
WHEN 'FIELD' IN ('Level 12','Level 13','Level 14','Level 15','Level 16') THEN 'Level 12 - Level 16'
END
Re: Caculate percentage in same month when using two date columns in same data table
You should restructure your data so that it's stacked so you have one row per observation (sales or service)
Unit ID | Date | Date Type
1 | 1-Jan | Sales
2 | 2-Jan | Sales
2 | 2-Feb | Service
Then use some beast modes to count your sales and service units:
COUNT(CASE WHEN `Date Type` = 'Sales' THEN `Unit ID` ID END)
COUNT(CASE WHEN `Date Type` = 'Service' THEN `Unit ID` ID END)
COUNT(CASE WHEN `Date Type` = 'Service' THEN `Unit ID` ID END) / COUNT(CASE WHEN `Date Type` = 'Sales' THEN `Unit ID` ID END)
This way everything is on the same date field.
Re: Description for Calculated Fields
So much cleaner! And it could just be right there in the tile under the beast mode name and pop up when you hover, just like any dataset field. YES PLEASE!!!
Re: Partition By not working to show correct SM% when I change parameters view options
Your case statements don't have any clause for when Geography/Product View = 'P&L'
Either add an else 1 at then end of each case statement, or call out a specific value for each option that the user can select.
Re: Magic ETL Organization Tiles
This is another idea that has been requested time and again. I think @Ashleigh has requested it a lot previously. (If it was someone else, oops!)
I find myself wanting it SO OFTEN!
Addendum to the screenshot above - I would like to see it not necessarily fully detach the sections, but to simply be able to identify sections and note what is happening in that section. It would also be cool if those sections could then be moved around together, but not a deal breaker.
Re: replace a Dataset within SQL workflow and within transforms
it is possible. you'll notice that in your screenshot the name of the dataset is aliasedfrom EmploymentCycleUpgraded to employmentcycleupgraded.
if you wanted to swap in a new dataset to your ETL, just add it in and then change the alias.
Re: Managing Data Retention Policy
You could utilize Magic ETL dataflows to check the date on the data and either split it out and archive it or remove it from the dataset depending on your company's data retention policy.
Re: Domo IDEAs Conference - Beast Modes - Number Formatting
Is there any hope of Domo implementing the SQL FORMAT() AS function?
This kind of workaround should not be necessary.



