Best Of
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
App Studio text box - hyperlinks limitations
Hi,
It seems that Hyperlink options in the text box App Studio allows inserting only https hyperlinks. (it's indicated : Must begin with https://)
Is it possible to add mailto : link so users will be redirected to Outlook ?
Thank you,
Oleksii
Oleksii
Smaller Sticky Notes
Allow sticky notes to be two grid spaces tall and two wide (currently they can't be smaller than three tall and three wide). This would allow for notes the same size as tiles, which is great for placeholders.
brycec
Duplicate Sticky Notes
Add a way to duplicate a sticky note. Having to restyle a note every time I create one is tedious. If I want the same style of note (which I often do), being able to duplicate and just change a few things like the text would be very convenient.
brycec
History Keyboard Shortcuts for Undo and Redo
It would be very helpful to navigate the new history with Ctrl + Z and Ctrl + Y for Windows and Command + Z and Command + Shift + Z for MacOS for undo and redo actions.
brycec
Change Certification from Datasets to Dataflows
Certification is currently requested and managed via a dataset, however we've found that in some cases changes to the dataflow don't cause the certification to expire. This introduces potential risk in cases where changes could be made that affect the accuracy of the data, but the dataset could still be flagged as Certified.
Also, although it's a minor issue, there's no indication on a dataflow that an output dataset is certified or not. So a developer could mistakenly update a dataflow breaking certification.
Additional rules could be put in place from a DOMO technical perspective, however I believe a better option would be to move the certification to the dataflow.
By certifying the dataflow:
- The actual object that governs the data accuracy/quality in the dataset/s is certified
- This could enable a visual reminder within the ETL to a developer they are editing a certified object
- The output dataset/s could inherit the certification from the dataflow
- If certification is broken/expired, this could then result in the certification of the output dataset/s expiring
- Better management of the certification would be enabled through the versions of the dataflow, as soon as a new version is created, certification should break/expire
- It could also enable quick rectification of accidental certification expiration by reverting to the prior certified version of the dataflow
This next part is possibly a stretch, and would undoubtedly require some expansion to the metadata of datasets/dataflows, but this could also enable the connection of certification between multiple datasets within a lineage.
For example:
- dataflow B is certified using certified dataset A as a source
- someone breaks the certification on dataflow A
- dataflow B certification then breaks, triggering an alert to that dataflow owner/s and subsequently removing certification from dataset B
This would enable proactive management of full dataset lineages, encourage certification to be applied/broken taking downstream effects into consideration, and encourage the use of certified objects more due to the added governance this brings.
Alerting and configurable options for Watchdog
Currently, any watchdog job created in the UI runs every hour to check for errors. For example, I use dataflow errors to monitor the execution of critical flows. These flows may run weekly, daily or hourly.
When a daily job fails, the watchdog will send the same error message every hour, resulting in up to 24 messages (if integrated with a Slack webhook) about the failed dataflow. While this might be appropriate for hourly jobs, I expect to receive only one error message per failure for daily jobs.
The main issue with the alerting system is its frequency—receiving too many alerts can lead to them being ignored. Ideally, the following configurable parameters should be added:
- alert me once job is failing/ alert me every time watchdog runs
- frequency of watchdog executions should be configurable (e.g., every day, every 5 minutes, every hour, etc.).
With these two parameters, we could better fine-tune the alerting system.
Oleksii