Best Of
Require High AI Readiness for AI Chat use with Datasets
Hi, I think it would be a great feature to require datasets to have high AI readiness in order for AI chat to work with them. This would improve the results of the AI chat outputs and would create better data governance around the metadata and definitions. This should be a feature to be turned on/off by an admin of the tenant. Maybe it's tenant wide or maybe it's based on roles/groups.
zacpolin
Waterfall Chart that allows for intermediate results
Hi, we are currently not able to built a waterfall with intermediate results using the waterfall chart in domo. It is somehow possible with a workaround using the bar chart to create bars that reflect an intermediate result step. This would be super useful, since for now we are opting out for other solution that are more effective and efficient when it comes to waterfall representation - however are not updating automatically and do not allow for filtering. This has a high need in our organisation and would find a wide usage base.
Update Domo's version of R
Right now, Domo uses R 4.1 in Jupyter and in the data science tiles. That version is over 4 years old and increasingly is not supported by packages, making it harder to use common packages in Domo. Please update to 4.5.
Dynamic Values for Scale Markers
It'd be good to have the ability when using Scale Markers to use Fields and Aggregations just like you can do for Summary Numbers. Even on a basic bar chart, if you use the Average, it just does an average of the Totals Shown, rather than the actual average of the field being used for the Y Axis, so if you show Average on both places it'll give you a different number.
Having options like this instead would be awesome and could help visually provide answers to common business questions like easily visualize performance against peers.
Controlling Page-Level Access in App Studio
See post from community forums. In short, it would be great to be able to control access within an app at the page-level to hide or show pages for different groups.
Controlling Page-Level access in App Studio - Domo Community Forum
Mags
Allow Group Ownership for DataFlows
I know there is a feature to update groups to own a dataset. If we can have group ownership for dataflows as well, that will help track dataflow failures as a team.
Ability to share filter view with a specific person and not to everyone
Give the capacity to share filter view to a specific person / group.
Today, either we have the option to not share it at all or to share it with everyone.
It creates useless noise for users. Having the capacity to share filter to only the needed users, would help the user experience.
Adding Subpages to Company Pages
When adding a new subpage to a parent page, it is very easy to go to the navigation menu and click on Manage Dashboards and then click "Add a sub-Dashboard" under the parent page where I want the new page to exist. However, if the parent page is part of the Company Pages, those pages are not shown in this list. I have to click Add a Dashboard and create the page, then go to Admin Settings -> Pages and find the new page, select it and choose Move and select the parent page that I want it to exist under.
It seems like Admins should have the ability to directly add a subpage to a parent page through the navigation menu since they have the rights to manage pages and not have to follow two different processes when adding a subpage to a parent page.
Smart Text as a Variable
At the card level it would be beneficial to know what the current operating environment is for a card and leverage that information in a beast mode.
For example, if there were a "system variable" that stored what the current "Graph By" selection is, like what is already available in Smart Text, then you could have a beast mode that is responsive to that selection.
Re: Improve Readability for Long Column Headers in Color Rules Dialog
This is needed in various other dropdowns like the Save As for cards, dataset selection etc. Any dropdown for dataset or dashboard selection should be much wider. For dashboard dropdowns, the dialog could wrap by separating the names of each sub-dashboard onto a new row underneath the top dashboard.
