Best Of
Add Card Description in scheduled dashboard email
Currently the card description is missing in the scheduled dashboard view in the email. Would you be able to add that so our audience can see the details I listed out for them?
Domolola
Auto Data Replace in Drill Down Cards
We build of a lot of drill down cards however when the cards are duplicated, we would update the dataset of the parent card however this does not automatically update the child / drill down cards, it still maintained the original dataset it was duplicated from.
There should be an option to replace all the child and drill down cards with the updated dataset from the parent card since all checks are already done at the parent card level.
Custom Border Options Between Cards
In other BI tools, developers can customize borders such as vertical and horizontal borders, to help visual differentiate them. This feature is especially useful for clients who prefer to have clear visual separation between cards in their dashboards. Currently, Domo lacks this level of border customization. Implementing this feature would enhance the ability to organize and visually structure dashboards more effectively. Is there a way to add border options between cards in Domo, or can this functionality be considered for future updates?
Please allow to be saved as a PDF or PPT
Can you allow for an app studio to be sent via a pdf or ppt?
Easy dataset field width extension
Hello,
We often use Domo datasets to store responses from our LLMs and need a way to easily extend the width of the response column beyond 1,024 characters. Currently this requires working with the Domo engineering team. Is it possible to bypass that process and manage column widths directly in Domo? Perhaps in the Governance toolkit? That would save time and allow greater flexibility in managing our pipeline.
Thank you!
MC_Creed
Governance on New Navigation Features
Can we have the ability to control which “Features” are visible and available to users?
Even though there may not be any actions the users do with them, it opens it up for many, many questions around whether they should be doing more or seeing more.
- Example: Code Engine is not something all users would use but with it available to view, it may cause confusion.
cochoa
Reduce Clicks On New Navigation
To reduce clicks in the new navigation, I would like the ability to select the top-level page when viewing subpages. In the example below, once I click on the > to expand and see the subpages, I cannot go back to the content on the top-level unless I select "Dashboards". I want to be able to click on "NPS Division" directly. Shown below in red.
cochoa
App Studio - Targeted Page Sharing
Hello,
I currently have an AppStudio that has two pages, one page serves as support to the main one. The support page is supposed to be used by a select group of people responsible for feeding and driving the main one. The main one is to be used by all users with access to the app. It would be great if I could share the support page only with those individuals (essentially hiding the page from other users), so that it all stays in the same app.
Would love to hear ideas, and perhaps a solution that I'm not aware of 😅
Thanks!!
Ever wished you had more space in the formula editor?
The days of trying to construct a long and complicated formula in an itty bitty little formula editor are over - you asked and we heard you: we've now added the ability to collapse the Tools section of the expanded formula editor in Magic ETL. This went live in your Domo instance yesterday. Just open the expanded formula editor in one of the tiles where you write formulas (Add Formula, Join Data, Filter Rows, or Group By) and click the caret on the Tools bar to collapse all of that documentation and noise. Click the caret again to bring it back when you need it for reference.
My team and I love being able to slip in these little quality of life updates, amid our bigger feature efforts. We hope this makes the process of writing that formula more pleasant and improves your life just a little bit.
(…although I hate to tell you this, but that massive CASE statement should probably really be a join to a lookup table. #justsaying)
— Your Friendly Neighborhood Magic ETL Product Manager 🙌
