Best Of
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 |
Oleksii
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.
Permanently dismiss App Studio banner
The stock photo woman with glasses has been replaced with the "Getting started with App Studio". I have clicked the x multiple times and it keeps coming back.
Content Access Requests eMails Direct to Content when Buzz is Disabled
Whenever someone requests access to a specific card or page, we will receive an eMail in our Outlook inbox, but when we click on the link in the eMail, it takes us to the Main Landing Page instead of the content that was requested. This happens when Buzz is disabled. We're requesting that the link should redirect to the content itself for easier access.
Integrating Microsoft Teams with Domo Alerts
Integrating Microsoft Teams with Domo Alerts would enhance real-time communication and collaboration by delivering alerts directly within Teams. This integration would to reduce reliance on email, streamline notifications, and improve response times.
Currently, Domo Alerts are primarily delivered via email, which can lead to delays in response and action. Emails are often overlooked or buried, especially in high-volume inboxes, reducing the effectiveness of critical alerts. Implementing Microsoft Teams integration for Domo Alerts will allow alerts to be sent directly to Teams channels or individual users. This will leverage Teams' real-time communication capabilities, ensuring that alerts are seen and acted upon promptly.
Proposed Benefits
Improved Real-Time Communication. Teams is designed for real-time communication, making it an ideal platform for urgent alerts.
Enhanced Visibility. Alerts in Teams are more likely to be noticed and acted upon quickly compared to emails.
Streamlined Workflow. Integrating alerts into Teams reduces the need to switch between platforms, enhancing productivity.
Better Collaboration. Teams' collaborative features allow users to discuss and resolve issues directly within the alert thread.
Reduced Email Overload. Shifting alerts to Teams helps declutter email inboxes, allowing users to focus on other important emails.
CBrowne