Best Of
Re: Dynamic Variables should dynamically change formatting as well
A further improvement would be to allow variables to be referenced in things like table headers.
Jones01
Re: How to secure our form brick when embedding forms publicly
Embedding a form brick without authentication is not safe for collecting sensitive data or PII. It exposes security, privacy, and compliance risks.
A work around would be a 3rd party secure form like Google Forms. You can then ETL the data into Domo via connectors or API. Otherwise, as I mentioned - run the form submissions through a secure HTTPS endpoint that you control.
Re: Being able to edit "Home" Button on Apps
I agree with the above— I was really hoping the Home icon could be customized to point to a URL of my choosing. Greater customization with the navigation bar would be greatly appreciated, e.g. modifying the actions and adding our own buttons.
Dorien
Re: Group ownership of dataset should allow anyone in group to submit for certification
Absolutely, having group ownership for cards is super useful. I have no idea why the same logic does not apply to group ownership of datasets
PowerPoint add-in extremely slow refreshing all content
I have a fairly large PowerPoint with a lot of Domo cards in it. When refreshing individual cards, they take about 20:seconds, but when I hit refresh all, it just spins for hours. Is it simply due to the volume of cards? It’s a pain to refresh each one individually, anyone have any luck with this?
thinen
Re: Calculate Percentage of Total
Here is how I typically do this sort of thing:
SUM(CASE WHEN Status in ('Clinic','Surgery') THEN 1 ELSE 0 END)
/
COUNT(Status)
Using 1's and 0's allow you to use the sum function. Then divide it by the count of all the status.
Re: Use loops to avoid rewriting case statements within a beast mode many times
There's an edge case which is causing the wrong labels. Try the following:
CASE WHEN `maint_count_between_restarts` = 0 THEN 0 WHEN `maint_count_between_restarts` > 50 THEN 50 ELSE CONCAT(FLOOR(`maint_count_between_restarts`/5)*5+1, '-', FLOOR((`maint_count_between_restarts`+5)/5)*5) END
Re: only show data for next 30 days
CASE
WHEN `Next Cycle Count` BETWEEN CURRENT_DATE() AND DATE_ADD(CURRENT_DATE(), INTERVAL 30 DAY)
THEN 'Upcoming in Next 30 Days'
ELSE 'Outside 30 Days'
END
This would give you a field you can use to list or filter.
CASE
WHEN `Next Cycle Count` BETWEEN CURRENT_DATE() AND DATE_ADD(CURRENT_DATE(), INTERVAL 30 DAY)
THEN 1
ELSE 0
END
Re: only show data for next 30 days
Sorry…I'm in on a conference call…lol
CASE
WHEN `NextCycleCount` >= CURRENT_DATE()
AND `NextCycleCount` <= DATE_ADD(CURRENT_DATE(), INTERVAL 30 DAY)
THEN 'Show'
ELSE 'Hide'
END
ItemID,ItemName,NextCycleCount
1001,Widget A,2025-07-10
1002,Widget B,2025-07-15
1003,Widget C,2025-08-01
1004,Widget D,2025-07-08
1005,Widget E,2025-09-01
1006,Widget F,2025-07-25
1007,Widget G,2025-06-30
1008,Widget H,2025-07-05
1009,Widget I,2025-08-15
1010,Widget J,2025-07-29
Re: only show data for next 30 days
You might also consider using the Date Filter using the Next option. This allows you to do it without writing a beast mode.
