Datasets Produce Enhancement Ideas
Can we get DOMOStats to include some of the additional information available on cards like in the API or CLI? While DOMOStats is great, there are some key funcionalities it lacks that are already available through the API and CLI and that would be a huge help when it comes to managing the instance. Some of the top of mind…
My descriptions in my AI Dictionary setup tend to be pretty close to what I would like for them to be in my column definitions. It would be cool if we had a checkbox (similar to Save to Dataset) that asks if you want to save that description to the column definition in the dataset as well!
It would be extremely useful if the Domo Stats workbench jobs could surface the query within the job, sometimes actually accessing Workbench can be a process and it would be great to quickly know what the query is without having to remote desktop to some obscure server.
It would be nice to have a Domostats dataset that shows dashboards and their cards. That way, when we go to delete cards, we can check if they are on a dashboard (or several dashboards) more easily.
It would be great if dataset developers had the ability to tag a column in the dataset as a "date key". In theory downstream when building cards, anytime a user creates a new card, Domo would default to adding this tagged column as the date field. I feel this would save card builders an infinite amount of time not having…
I would like to pull submissions into a card to review before I approve/deny them in the Approval Center. Currently, the only way you can access the dataset is after the approval/ denial takes place, which defeats the purpose of the Approval Center for me.
It would be nice when using the SQL Editor in the Views Explorer to have more context on why the query fails. Looks to be working pretty good on the SQL tiles in Magic ETL. When you have an error for instance in SQL Editor in the view, a line/character where the error occurs would help tremendously. Right now if there is…
Currently, Domo’s slicer/filter cards require manual selection of default values, which can be limiting for use cases where the default selection should change dynamically based on the current date or other conditions. I propose the ability to set dynamic default values for slicers using conditional logic. For example,…
When you have a lot of datasets/dataflows that share common fields.
When datasets haven't been actively queried in a while, they get auto-disabled, and need to be manually "re-started". When datasets like that are inputs to dataflows, they disable the associated dataflows. But, from the Datasets view of the Datacenter, we have no way of seeing that a dataset needs to be "restarted". It…
It looks like you're new here. Sign in or register to get started.
Have a Domo product enhancement idea? Submit or upvote on ideas in the Ideas Exchange.
Ask questions about Connectors, Workbench, Cloud Amplifier and get best practices from Domo peers
Ask questions about Magic ETL, SQL DataFlows, DataFusion, Dataset Views and get best practices from Domo peers
Ask questions about Beast Mode, Cards, Charting, Dashboards, Stories, Variables and get best practices from Domo peers
Ask questions about App Framework, Workflows, Domo Bricks, Domo Developer, API and get best practices from Domo peers
Ask questions about Jupyter Workspaces, R & Python Tiles, AutoML and get best practices from Domo peers
Ask questions about Domo Everywhere, Scheduled Reports, Mobile and get best practices from Domo peers
Ask questions about Governance Administration, Approvals, Teams, Alerts, and Buzz and get best practices from Domo peers
Watch how our Customers are using Domo to solve their complex problems.
Domo support and product teams are here to live-answer questions about the most recent product releases. Please post questions in this Forum board for all users to benefit (rather than submitting a support ticket).
Questions or discussions related to Domo University, trainings and certifications