Best Of
FOR WHILE loops in dataflows
Related to: https://dojo.domo.com/main/discussion/52378/is-it-possible-to-use-while-do-loops-in-mysql-in-domo-dataflows
There is no way to implement SQL Recursive Queries in Domo: https://www.sqlservertutorial.net/sql-server-basics/sql-server-recursive-cte/
Instead you have to guess the max depth and build as many JOINs and columns manually into your Queries / Dataflows.
----
It would be ideal to have a mechanism for executing a FOR / WHILE loop in dataflows.
Use cases for my organization include, we have a writeback connector that due to the vendor's API restraints can only receive 1M rows at a time.
If we knew our dataflow could have up to 7M rows, we'd have to implement 7 writeback connectors in the dataflow each with a LIMIT / OFFSET function built in.
Ideal state would be to do a FOR WHILE loop that would handle pagination.
---
If you were doing any sort of bill of materials reporting and you wanted to structure your data so that you knew "for each recipie which items are part of this recipie" you would have to know the maximum depth of all work-in-progress recipies.
ex. I want to know all the components of a Subaru Forester. I'd need to know the components of an engine. each engine is composed of pistons... and stuff. each piston is composed of ... gaskets and rods. each gasket is made from ... stuff. In order to build a report that captures the full BOM i'd have to know the depth each WIP goes to.
DataSet Scheduling Hub
It would be nice to have a centralized place to view and manage the scheduling for all existing DataSets.
Fix HTTP 413 Errors when logging into multiple instances
For those of us that need to log into multiple Domo instances during our day, we will often get greeted with this error.
The fix is to close your browser completely and then you can log back into your Domo instance. This is a very frustrating issue, particularly when you have multiple tabs open comparing things in multiple instances. You seem to be limited to only 3 or 4 instances before the issue comes up and renders are instances useless in your browser.
Please fix this so that there is not a limit on how many instances you are logged into in your browser.
Edit Bar Charts more dynamically
Hi,
I was hoping we could begin using Color rules a bit more dynamically. I was hoping we could assign color rules to different fields in the Card. For instance, elements that are not being used in the Bar chart but elements outside as well that are impacting the Bar chart directly
For instance, if I have 3 variables in the filter section. Lets say the month variable. The variable s can be "this month'", "last month" and "this month last year". I want to be able to add color rules to these variable even though they are not a part of the x-axis, y-axis or series part of the Bar chart.
This would mean as the months progress I would not have to manually update the color scheme I choose. Currently. I need to do that each Month as illustrated in the picture below
Here the "Test" Column sits in the Series part of the bar chart and is filtered by a beast mode. If I could add the color rule to the beast mode, I would not have to change the color each month and it would be more dynamic.
Bug Update: Filtering on Null Values
Past May @SamEich posted a bug regarding Null values. Basically the filters you add to a Domo card are not able to filter on a null value. I ran into this problem several times and the bug still does not seem fixed. How could we know the status of this request and when it will be implemented? Should I contact Domo Support? Bugs like this should be addressed quickly.
Thanks!
Re: Forecasting best practices
At a high level, here are a couple of tips that I find helpful.
First, look at your actual transactional data to see what dimensions are important to you. Once you determine the actual dimensions that are of value, create a forecast sheet that includes those dimensions. Just remember, the more detailed you are with dimensions the more lines of data will be required in your forecast. However an hour or two of pre-work when setting the forecast can allow for much more detailed tracking throughout the year.
Second, make sure the metric and dimension names in the forecast align with those in your actual data. Without that, it is much harder to set up cards to show comparisons.
Third, we often place the forcecast data in a Domo online form, so it can be accessed and updated as needed.
Lastly, coming up with the forecast numbers is a bit of art and science. Obviously a good place to start is with prior history. But internal initiatives, market conditions, and other changes will affect future performance.
If you have more specific questions, feel free to post.
Ability to add Annotations at a data set level
Finding that there are a lot of data caveats or annotations that need to be applied to multiple cards/dashboards. Being able to call out data caveats at a data set level, where any user building a new card off of that data set the annotation would be automatically added to the card if the given time frame is included in the visualization. Abilities to include or exclude annotation in the view would be helpful, which i believe already exist, but further functionality could help.
ANNOUNCING SKI DAY: Join Us In Person for Domopalooza 2024
At this year’s Domopalooza, we’re making “aha!” moments happen everywhere—even on the slopes!
Round out a week of insights and entertainment by joining your peers on Friday, March 29, for a fun-filled ski day at Snowbasin Resort! Registered attendees need nothing more than a valid ID to qualify for a complimentary lift ticket and rental gear.
Transportation to and from the slopes is provided free of charge.
Register Now
💪Community Networking and Training: Build your Domo skills and get inspired—because your next great idea might be sitting next to you.
🗣️ Visionary Speakers and Product Announcements: You’ll hear it first: AI, apps, and what’s new in Domo for 2024.
🎤Two Nights of Entertainment: Enjoy two nights of concerts from A-list performers.
👩🏫 from our incredible customers: This year’s event is all about empowering you with data experiences that spark bold curiosity and power legendary business impact.
Number Formatting and abbreviated Numbers
Could we add the chart property 'number format' to table cards and could we have it that we could partially abbreviate numbers. For instance, 1.1567B could be 1156.7M. And other such similar features.
Group By "Concat Distinct" Now Live!
I wanted to make a quick post to let you know about an update we made to the Group By tile in Magic.
In your instances, you should now see the ability to choose a new options when defining how a column should be aggregated in the Group By tile:
- Combine distinct strings separated by ,
This allows you to create an aggregate column that includes a list of distinct values rather than having to choose just the first/last value, a count of items in the aggregation, or a non-distinct list of values.
(Note: The equivalent in an expression/formula would be GROUP_CONCAT(DISTINCT argument SEPARATOR ', '))
While relatively minor, we think this change will make using Group By in Magic just a little bit nicer.
Let me know if you have any questions or thoughts.
Thanks!
Andrea (your friendly neighborhood Magic Product Manager)







