Analyzer Product Enhancement Ideas
One of the most common issues I encounter when troubleshooting cards is that the date range is based off of the wrong date field. Currently it's too easy to not notice which date field is being used since users cannot see the date field unless they specifically open the date range settings in Analyzer. It would be helpful…
The recent gradient color addition to Analyzer has the potential to eliminate the need for setting up a bunch of color rules for variance colors, but it needs the ability to set a midpoint value like the heatmap color setting on table cards. Currently the gradient colors are relative to the bars displayed on a chart…
Each time a quick filter (selection) is added, all options are selected by default. While you can manually deselect all before saving, it would be nice to have a company setting or other global option to always have quick filter selections deselected by default.
Ability to choose if you want to exclude a selection, or a select all feature on filter cards. Currently, with the multi-select feature, if you want to exclude one selection you must individually select every single line item one by one except the one to exclude. If you could 'select all' then deselect the one(s) to…
Currently, you can set column widths under "General" properties of a regular table, but not a pivot table. This doesn't allow us to maximize space on the page.
The Pivot table view on a Datacard only allows to add upto 10 rows/columns to the visualization. If we try to add additional rows/columns it starts replacing the existing ones with the new row/column. There should be no limitations to the Datacards as it could vary based on different views we require to visualize our data.
I know I can do a max (`datefield`) over () in a beastmode, but this only works for card level filtering and not page level filtering due to the fact that this is an aggregation beast mode. For the page level, it requires a rank and window in a dataflow. Both of these work arounds break any smart text that would refer to…
It would be a huge QOL improvement for our company if filter cards could have a default value selected (the most recent date, the first value in ascending order, all values that equal a specific string, etc.) because many of our dashboards need to have a single filter value selected to display accurate data. For example,…
It would be great to be able to export tables I make while editing cards without saving them.
DOMO should really consider adding a feature to require an option selection by the user when a developer configures a page filter card. This would coerce the underlying dataset to subsetted in order to prevent double counting in some cases.
It looks like you're new here. Sign in or register to get started.
Alerts Product Enhancement Ideas
API Product Enhancement Ideas
Apps Product Enhancement Ideas
Appstore product enhancement ideas
App Studio Product Enhancement Ideas
Beast Mode Product Enhancement Ideas
Buzz & Navigation Ideas
Charting product enhancement requests
Cloud Amplifier Product Enhancement Ideas
Code Engine Product Enhancement Ideas
Ideas or feedback for the Domo Community or the Community Forums.
Connectors Product Enhancement Ideas
Dashboard Product Enhancement Ideas
Datasets Produce Enhancement Ideas
Domo AI Product Enhancement Ideas
Domo Bricks Product Enhancement Ideas
Domo Developer Product Enhancement Ideas
Domo Everywhere Product Enhancement Ideas
Federated Product Enhancement Ideas
Product enhancement ideas for Domo as a whole
Governance & Security Product Enhancement Ideas
Jupyter Workspaces Product Enhancement Ideas
Localization product enhancement ideas
Magic ETL Product Enhancement Ideas
Mobile Product Enhancement Ideas
Reporting Product Enhancement Ideas
Product enhancement ideas for Sandbox
Software integrations product enhancement ideas
SQL Dataflows Product Enhancement Ideas
Variables Product Enhancement Ideas
Workbench Product Enhancement Ideas
Workflows Product Enhancement Ideas
Other Product Enhancement Ideas