Best Of
Re: Add scroll to HTML Table
@BenSchein : Kindly help us with this request on priority please. Or we need to get the color coding in Mega Table. Your kind & urgent assistance would be much appriciated.
Regards,
Tejal Govila
Re: Remove row from dataset
Adding to what Jason has stated…
Domo does not support deleting an individual row directly from an existing dataset, but you can effectively remove a bad row by republishing the dataset without it. A common approach is to use Python to read the current dataset via the Domo APIs, drop the offending row (for example, filtering out a row where a column equals its own header name or is mostly null), and then write the cleaned data back using a full replace. Alternatively, you can create a Magic ETL that filters out the problematic row and have downstream ETLs and cards point to the ETL output dataset instead. In both cases, the row isn’t deleted in place; the dataset is replaced or superseded with a version that no longer contains it.
Re: Calculating Time Difference
I forgot to reply and say thanks! This is exactly what I needed to get the visualization across the line!
Jessary
Re: Pivot Woes - Losing Rows causes total to change
When you pivot in Domo, the pivot expects the incoming dataset to already be defined with the fields you want to pivot on. If you include extra fields, the pivot will collapse those rows and cause things to dissapear.
The "Group By" forces the dataset to the right fields before you pivot. You are aggregating (SUM, COUNT, AVG, etc) all the details. Which produces one row per Dept + Month + Actual/Budget so that the pivot doesn't have to aggregate.
Re: Your First Look at the Domopalooza 2026 Main Stage
Let's go!! Can't wait for my first DP 🙌
Re: Your First Look at the Domopalooza 2026 Main Stage
I will make sure to find you during one of the days, gotta make sure I meet the legendary @Data_Devon in person!
ellibot
Re: Top N Filter Not Working as Expected in Multi-Series (Grouped) Bar Chart
Ahh.. If you are using the nested bar chart, you can accomplish this without any special fields.
Remove the filtering and sorting and then go to chart properties - general and choose Sort on Totals Descending and Maximum Items 5. These two properties act differently than the Limit Rows and Sorting features and should get you what you want. You can see my screenshots below using the Example Sales Data.
Re: "I Just want the numbers" - Accomodating Domo detractors
To Colemen's point, I'll plug "Dashboards that Deliver" as a good read for this. The first 11 chapters are all about practical steps to define the purpose, profile the users, and prototype with the users involved to make sure the final product really meets their needs.
One thing they push, is before jumping to the technical implementation (Domo dashboard, Google Sheet, static email, etc.) create some sketchy prototypes of what you think the product should look like. (literal sketches, or wireframes, or simple PPT). Show them to the potential users, get feedback, and iterate. You're more likely to get high quality feedback on a low-tech prototype and you'll be more likely to make big changes because the lift to change it is lower.
Re: "I Just want the numbers" - Accomodating Domo detractors
Users can kind of be bucketed into different user types. Sort of like customer profiling, you can think of it like internal customer profiling. Your customer profiles will be somewhat unique to your company. They may look like:
- Tech forward (embrace Domo, want to do more with it, hungry for new features)
- Resisters (prefer the old way. Spreadsheets, powerpoints, etc…)
- Casual participants (view a couple of cards or apps, log in weekly)
I'd recommend going through an exercise to profile your customers and consider how you might approach each profile differently. For example, for the Resisters - which is the group your post is trying to serve, you may need to consider Scheduled Reports using Report Builder. Or using the Powerpoint plugin to create monthly slides. Or using the Google sheets plugin / writeback to update a spreadsheet. Or explore the new Worksheets feature in Domo. I've found that that gets them to dip their toe in and start slowly using Domo features. The hope is that they evolve into a different profile that uses more of Domo, but if they don't, at least they are still benefitting from Domo in some way.
You can't approach each user profile the same way, or you will likely fail. Domo has a lot of content types and different features because the needs of users are all different.
