Best Of
Re: App Studio - Limits for Control Filter Options (Please!)
Very helpful feature. Certainly filter cards can be used to overcome this. But It would be good if this functionality can be provided on page filters so we don't need to explicitly create filter cards and consume unnecessary space on the dashboard. Additionally it would be good if the setting can be provided to make page filter single/multi select. Today we can do this on filter card. So even if single select is used from filter card users can still use multiselect from page filter. Ex Currency filter. If people uses USD & LC both then it will aggregate both currencies and data would be incorrect. This is must have feature on page filters.
Re: what kind of SQL does DOmo use
Domo uses the MySQL dialect. Here's a few references:
https://domo-support.domo.com/s/article/4405337525783?language=en_US
Is there a best practice for a visual indication that a card has a drill down configured?
I'm curious if the community has recommendations for a quick visual cue to users that a card has a drill down option configured. I think maybe I saw a method that @ColemenWilson was using at one point (…?) but figured it might be worth a post/ask to see what others are doing and maybe what they do (and don't) recommend. Thanks all!
Re: beast mode for total active tickets per hour
An hour bucket is a way of grouping timestamps by the hour they fall into. So for example:
| Hour Bucket |
|---|---|
2025-05-20 08:23:17 | 2025-05-20 08:00:00 |
2025-05-20 08:55:42 | 2025-05-20 08:00:00 |
2025-05-20 07:05:10 | 2025-05-20 07:00:00 |
It's saying "group everything that occurred between 8:00 and 8:59:59 under the bucket for 8:00. You have this in your formula. You are doing it in your screenshot. You are counting tickets grouped by that hour.
DATE_FORMAT(`Date_Entered_UTC`, '%Y-%m-%d %H:00:00')
If you want to show them by the hour only (8:00, 9:00, 10:00, etc), you could try
DATE_FORMAT(`Date_Entered_UTC`, '%H:00')
Oh, by the way…I would separate date as a column formatted as short date such as 5/20/2025 and hour as another column. Then put each in the sort to arrange them ascending or descending and include maybe year and month columns if this chart spans a long period.
Re: Can't find beastmodes to add to AI dictionary
Hi Ken,
All of our beastmodes are saved to a dataset. We had a call with our Account Manager last week and it looks like it's a bug. When we save "edit" then re-save the BM then save the card, it will appear as an option in Ai Dictionary (after refreshing the page)
Thanks!
Josette
jvsering
Re: Implementing Card Navigation Settings that already existed in Dashboards.
@khushboo_ This is not an intuitive solution. I would have to click details at the bottom left of the page, then click on the edit button on the top right of the page details and then I will be able to click on the card to get those settings. As you can see, that is still more clicking and moving the mouse around than simply adding a card option button on each card. There is no need for me to "edit the entire page" if I want to edit a singular card.
Your solution also doesn't cover the breadcrumb issue I have brought up. What I don't understand is why are dashboard cards equipped with these capabilities, but these app studio cards aren't if app studio is designed to be an upgrade from dashboards.
Re: More customization in text cards
Why do we have the option to bold or use italic but not underline?
Also, you can't change the color of the bullets or numbers, they don't match the text and you are also able to adjust the size, so when you select header, title, subtitle etc, the bullets or numbers don't match in size with the text.
Jessica
Re: Can you help me understand why SQL Transform takes so long to run and how I can make it faster?
I agree with all of @ggenovese's recommendations for optimizing the SQL. If you're still not satisfied with the performance after implementing those suggestions, you could also consider replicating this in Magic ETL (still following the previous guidance). I've seen some significant performance improvements since migrating SQL dataflows to Magic ETL, most notably since Magic can process multiple steps concurrently, while the SQL transforms can only be run sequentially.
Re: Can you help me understand why SQL Transform takes so long to run and how I can make it faster?
I'd recommend that you break up some of the work into separate transforms. For example your B sub query could be a separate transform that's joined in to the main transform. You can also pre-filter A in it's own transform and then do your joins.
After you have parts segmented out into separate transforms you can review the execution times of each transform to see which parts are taking longest and make modifications.
Finally, I'd recommend leaving your dataset in a more granular state and letting analyzer do the aggregations instead. This may ultimately be a more flexible design, and I find that Analyzer can perform aggregations very quickly.
Re: Searching by Graph type in my instance
Sometimes I don't remember key words in the title of a card, but I remember what it looked like. Other times, there may be multiple cards with similar names and it would be helpful to further narrow down the search.