-
Dataset reference in Python by identifier instead of name
To identify input dataset by identifier instead of name, very useful for working with Python modules, as right now you need to update the source code when changing a name.
-
More customization in text cards
Allow more customization in text cards (line breaks, text size and color...etc)
-
Barchart behaviour when the sorting criteria doesn't match the fields shown
Barchart has an umpredictable behaviour when the sorting criteria doesn't match with the fields shown in the card
-
Multiple outputs for Python modules
Python boxes in the Domo ETLs allowing multiple outputs.
-
More dynamic elements in the cards
It would be very useful if not only the "Summary" but also the titles of the cards could be made dynamic. In the summary you can put fields that do not exist in the visualization while in the title you can only put certain limited fields (filters, date, etc). It would be solved by allowing the inclusion of a field,…
-
More info in logs
It would be very useful if, when executing a Domo ETL, a log file was generated to see the details of potential failures in the process. Currently, if there is a failure in any of the Domo's own boxes, you see that the process has been interrupted in a part of the process but we don't see the details. Also, if the process…
-
Dataset ownership for users groups
Being able to designate groups and/or several people as owners of datasets, dataflows
-
Dashboard description
Include a functionality that allow adding a description in the title of the dashboard (or, failing that, a tag)
-
Dynamic quickfilter values by default (ie last month)
Being able to tell DOMO that by default the card appears filtered by values that are not always the same. Right now you can only point to a specific value but you cannot enter a logic so that, for example, it selects the last month.
-
Drill down & quickfilters improved communication
When Drilling Down from one visualization to another with different datasets: to link the filters that are created when drilling down with the quickfilters. If I want to continue browsing a visualization, it becomes inconvenient to have to delete the specific filter created by drill down, in order to continue filtering by…
-
Fixed colors based on dimmensions / measures not used
In bar charts, being able to define a fixed color based on a value even if it is not used, for example, the maximum value, or a certain peer. We frequently required to highlight based on logic, such as max/min value, contains value, etc. There are a lot of scenarios where this feature would be handy.
-
Dual-axis settings
Dual-axis visualizations should have different settings at the element level, hover...Today, the settings are common for both axes, which means that the information displayed is often not optimal.
-
Table customization
Allow modification of table attributes: borders, colors... With the phoenix library (the one used by Domo to design tables) it is not possible. Customization options are very limited.
-
Quickfilters Hierachy
Define hierarchy between quickfilters. Currently any selection in a quickfilter affects the rest of the filters and it sometimes causes values in filters to "disappear", while other filter has to be deselected for them to reappear- It is not something intuitive for the user.
-
Quickfilters alternative sorting
Quickfilters are always sorted alphabetically. To work around that, we have to add a numeric prefix to the values to sort them as needed, it would be nice if the quickfilter could be sorted by showing the original values.
-
Kind of footnote
Possibility of adding a note. Currently domo allows annotations on the data series, it has a summary field, the title and the description. None of these options covers the need to add a clarifying note that helps to explain the card, be brief and visible (with the function of a footnote to a text).
-
Ways to visualize datasets impact beyond first level
The direct impact and total impact information (about datasets, dataflows, cards and alerts) is only available by consulting the elements individually in the Domo interface, however it would be very useful to have this data in the DomoStats tables. The main use case is for the platform owners to have a centralized place…
