Analyzer Product Enhancement Ideas
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.
This discussion has been merged.
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.
I suggest an option be added to change the default chart type and column values for Analyzer. I almost never use the default bar chart in any case. So it's fairly annoying to open Analyzer, have to change the chart type and remove the randomly selected default columns. Especially if there is a large amount of data to be…
Current conditional formatting is very useful, however still quite limited in functionality especially with numeric and date values as these are static. A current workaround for this is to utilise HTML tables, or create additional columns for above/below the required targets, which gets quite messy. It would be hugely…
I would like for the ability to choose whether Pivot Tables expand/retract vertically rather than horizontally. Right now, each level is stored in it's own column. This often takes up a ton of unnecessary screen real estate. I'm envisioning something more like this… VS how pivot tables currently function
As a new initiative, we are attempting to create visualizations of "baseline" expected performance for aggregated actions measured on a monthly basis. These activities are the end results we expect from the efforts that our vendors make to drive traffic to our sites. We have artificially set the "acceptable" performance…
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