Best Of
Dashboard Page Filter: Automatically set a default value based on the available values in the filter
When a PDP policy is implemented to a dashboard, I noticed that we cannot set the page filters (i.e. single select filter) to a default value for each PDP policy or have the page filter automatically set to a default value.
This is because when there are mandatory dashboard filters in order for the dashboard to work intuitively, these get broken by the pdp policy, resulting in end users seeing as though the cards in the dashboard are broken. In order to workaround this, I have tried creating filter views. However, even then the filter views are not able to default to specific users which defeats the purpose.
janice
Enable AI chat only on specific Dashboard / Apps
Hello, I think it would be a helpful feature if we had the ability to enable AI Chat only on specific dashboards / apps. For example, only on production dashboards or only on specific cards that we feel confident having AI provide answers to our end users.
zacpolin
Re: 8/7 release issues
I'll second all these issues. While a UI update is a great idea the changes rolled out are pretty bad. Filter bars are being cutoff, visualizations got squished, we lost the padding on all of visualizations so they look off, and the PDP icon isn't able to be removed and as a result is blocking values on tables. Hoping this get's fixed soon 🤞
collinT
8/7 release issues
I am having to go in and modify every dashboard that I have filter cards on this morning. It appears the sizing has changed so everything is getting cut off. This is EXTREMELY annoying and time consuming.
Additionally, I have it set on all my dashboards to hide the PDP icon, but as you can see in the above screenshot the icon is showing since the release. While these things are minor they have a negative impact on UX.
ARosser
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.
