Best Of
New Navigation: Default View by User Group
Building on the planned New Navigation feature, I think it would be useful to be able to create a default view for specific user groups. For example, all members of a "Sales Rep" group have the same apps and dashboards pinned to the lefthand navigation panel.
Date Picker & Period Over Period Chart Enhancements
We have end users who want to set a date range and see the change compared to the corresponding previous period. Currently, in PoP cards, you can:
Set a comparison period on the cards that overrides the dashboard date picker
OR
Use variables and Beast Modes to create current and previous period calculations and add the Variable Control to your dashboard.
Note that there is no date picker style Variable Control, so you have to also set start and end date variables and use those in your Beast Modes.
If you try to set a custom date range / period for your PoP cards at the dashboard level, the comparison breaks.
PoP cards set to MoM:
PoP cards set to MoM, but user selects a date range with the dashboard level date picker:
Another example where a different date range is selected. In this case, the cards are set to Current Month, but still show the correct values when you select a different date period in the Date Rnage. Selecting the corresponding Chart by has no effect, and PoP breaks:
On top of the inherent complexity for a dashboard developer, this is clunky for end users and dramatically limits the self-serve utility of a dashboard, for a few reasons:
- PoP comparisons break when you use the dashboard level date picker
- PoP comparisons are locked into the setting on the card, inflexible
- Why is there a date picker, and why can I set a Graph By option, but I still have to enter the dates I want to compare in these control boxes?
It would be much more intuitive and user friendly if the dashboard level date picker could set the current period and then show the corresponding previous period change.
This might be accomplished a few ways:
- by a setting on the cards themselves that allows dashboard date picker override
- inherent override without a setting
There are some elegant examples in the BI application space. Data Studio solves the problem well, by basing the comparison period on the dashboard date picker selection:
In all 3 screenshots, the end user selects the date period they want to view data for, and the scorecard tile natively understands to compare to the previous period.
There is no additional programming required for the dashboard developer, and the end user can self serve by viewing all the data for a given time period.
Tool Tip Functionality for Table Viz
We pull our data from SFDC and have opportunity pipeline tables we review weekly. We have long string fields (Next Steps, etc) that I'd like to be able to provide functionality to view but not make part of the table itself since the visual formatting gets messy. If we had tool tips for tables I could add the long text field as a tool tip to show on hover and incorporate it seamlessly without messing up the table view.
Labeling Year to Date as Fiscal Year to Date when fiscal calendar is used
I'd like to suggest a small labeling change. If I check off the "Use fiscal calendar" box, I'd like to see "Year to Date" become "Fiscal Year to Date", and same with the Quarter date grain. I generally leave a note in the description that the year in question is fiscal, but having it labeled in the date selector seems like a better solution.
When clicking to filter, shouldn't the default be to INCLUDE the value???
Let's say I want to filter the page for the owner changes.
Since the slices get small, I have to use the legend to do that.
It excludes the values instead of filtering.
For extra fun, it also makes the page filter 'In' all the other values!
I am also providing an example, using a bar chart, since we would so clearly want to filter to INCLUDE on these the vast majority of the time.
Let's say we want to see the trend of owner changes:
NOPE!
This is something that has been griped about for a long time, but some of these little details seem like they take too long to document, so we just deal with them. However, on the particular dashboard I am working on, it's forcing me to change too much about my page so I am finally submitting this.
If someone else loves that selected series are excluded by default, please speak up. I am curious about the use case there.
Thanks!
Scheduled Report Bulk Management
Can their be a feature enhancement that would allow admins to bulk edit scheduled reports to allow a selected number of scheduled reports to be disabled, enabled, deleted, or the owner changed?
Remote Domostats Reports sync with Local Domostats
Hi Team,
Remote DomoStats (observability metrics) is an extremely powerful tool for collecting governance data from multiple instances into one centralized view. While each instance individually makes extensive use of Local DomoStats connectors, at a global level we are limited to using Remote DomoStats.
We’ve noticed that the list of available reports in Remote DomoStats is not aligned with those in Local DomoStats. Specifically, Local DomoStats currently offers 34 more reports than Remote DomoStats (comparison as of April 24, 2025). Additionally, the naming conventions between the two are inconsistent. For example:
- Local DomoStats includes reports named App Studio App Pages and App Studio Apps, while Remote DomoStats uses Data App Pages and Data App.
- Local DomoStats uses Dataflow Input Datasources, while Remote DomoStats uses ETL Inputs.
Our primary request is to have a synchronized and consistent list of reports between Local and Remote DomoStats. This alignment would significantly improve global governance and reporting capabilities.
Below is a prioritized list of reports currently missing from Remote DomoStats but available in Local DomoStats:
Report Name |
---|
Certified Content |
Group Owners |
Workflows |
AI Model Endpoints, |
AI Models |
AI Projects |
AI Services |
Beast Mode Datasource |
Beast Modes in Beast Modes |
Variables in Beast modes |
Columns Used in Beast Modes |
Variables |
Publication Summary |
Role Grants |
Deleted Datasets |
Sandbox Commits |
Sandbox Content Mappings |
Sandbox Promotions |
Sandbox repository access |
Sanndbox Repository permissions |
ML Inference Jobs |
Auto ML Trianing Jobs |
Connector Permissions |
Credit Usage |
Dataflow Tags |
People custom attributes |
Project Stages |
Projects |
Task Owners |
Tasks |
User Activity |
User Landing Resource |
Workbench |
Buzz |

SQL Editor for Views Explorer error messages as helpful as ETL SQL tile's error messages.
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 just a simple syntax error the message is always 'An issue has occurred during processing. We are unable to complete the request at this time'
Folder Structure In DOMO For Connectors/Data/Data Flows ect..
I find the current UI of DOMO tricky to navigate, especially when you get into the hundreds of connectors and especially for connectors where you have to query the same connector for precise data cuts.
You can use tags and predefined filters based on a search term, but I find these as workarounds.
Can we introduce the ability to add or categorise data into folder structures?
Mockup attached
Increase Limit Rows in Analyzer
Limit Rows in Analyzer currently prevents you from going beyond 100K rows.
Due to this current limitation, we are unable to use Domo's native filter capabilities in our stores to lookup items (as our list of items get cutoff at the 100K mark). Instead, we are faced with establishing a customized pro-code solution as a workaround; which is not ideal.
As a retailer with several hundred thousand items, which is not unusual, I would like to see this limit increased substantially (500K+) or be limitless.