Best Of
Drill Path Visibility
It would be helpful to be able to see when a dataset has been used in a drill path and which cards have a drill path tied to them.
buzz_boom
Re-order page filters
It would be nice if we were able to re-order the filters on the dashboard page. Currently if you want to change the order you have to delete and re-add them. If anyone knows of a better way, please let me know!
Re: Request for Topics
- +1 on Account Management. I have spent a ton of time creating dashboards to audit my instance (more advanced than just DomoStats). In order to monitor what is coming in, going out, and managing users (especially across multiple instances). Learning how/why to create custom roles would also be a good part of that.
- +1 on Domo Everywhere content. Best practices for creating published jobs would be good. Especially since each job creates a new federated dataset. I made a mess when I started and now I have to clean it up 🙃
- How to utilize new features once they come out, I always struggle creating content for my users regarding new features so then we just don't end up using them for a while. Having some concrete examples would be useful (ex. I never got to using Segments and I still couldn't tell you how to use them).
- Best practices for instance health. I have so many users creating so many flows and rows of data that could be much more optimized. Going over Magic ETL best practices for a clean instance and quicker run time would be useful.
- Creating alerts to manage data. This is one I learned to do myself by doing error checking in flows to create error datasets, making error checking cards, and more recently just putting alerts on a dataset. Knowing your data is wrong before it has time to make it to the end user is very useful.
Ashleigh
Re: Request for Topics
- How to optimize data pipelines in Domo (DSV, Magic 2.0, Upsert connectors, etc.)
- Dashboard design best practices (What makes a dashboard stand out? How do you tailor your dashboard to the intended audience?)
- More Domo Everywhere content!! This feels like a black box at times, as I haven't seen very many public-facing training videos on the topic.
Thanks Professor!! Love the new video!
Trigger Frequency Option - When All Datasets Updated
I think it would be incredibly useful to add an option in the Dataflow Settings - When Should this Dataflow run section. The option would be 'When all datasets have been updated'. So there would be 4 going forward;
- Manually
- On a schedule
- When selected datasets have been updated
- When all datasets have been updated
The current suggested method to add the dataflow to a schedule that runs after the last set is updated only works if run times are consistent. I have a lot of datasets that have large variations in run times and I spend most morning reviewing dataflows to ensure they were updated at the right time. I know I'm not the only one that experiences this issue.
Thanks,
Micah
View a dataflow's ETL without having rights to edit
Hi,
In our organization, we have tons of dataflows built. Often, I'd like to understand how a dataflow was built, including the processing steps in the ETL. The only way to view the ETL steps is to have edit rights to the specific ETL. Often, I don't need to edit the ETL, but I do want to see how it's built. It would be great if there was a way to view the ETL steps even without edit rights.
Thanks!
swoodums
'preferred' connectors - last update date - 'best connector'
with 26+ Snowflake connectors and 5+ Athena connectors, it's often difficult to know which is the appropriate connector for my use case.
the 'preferred' connector is a good start, but it would be ideal to
1) have more visibility as to what makes a preferred connector
2) have visibility on any under the covers behavior that may make a connector better suited for different use cases ex. JDBC vs Unload connector.
3) have the 'last code modified' date visible. If a connector hasn't been touched by the connector team in multiple years, it might encourage users to look at a more recently developed / updated connector.

