Best Of
💚 Meet the New Domo + Progress Community Management Team!
Dearest Domo Community,
We're excited to announce that the Domo Community Forum has been placed under new management at Progress Software! As part of this transition, I have been asked to take on the role of Domo Community Manager and joining me on this new journey are two very special individuals from Progress I'd like to introduce you to: @Nichol_Goldstein, Progress Community Manager, and @Mitchell_Drysdale, Customer Advocacy Manager. We hope to earn your trust over the coming months and years as we commit to supporting this Community and resuming Domo's legacy under Progress!
Get to Know Us!
Mitchell Drysdale - Customer Advocacy Manager at Progress Software
Hello everyone! My name is Mitchell Drysdale. I am thrilled to begin meeting you all. I've spent my career leading advocacy programs across B2B technology with some community experience drizzled in. I'm an enjoyer of the outdoors, trying to spend as much time hiking and cycling as I can. If you ever catch me on a video call or webinar and see the gaming setup behind me, you'll also realize I'm a bit of a gamer as well. I'm super excited to be involved in the community.
(LinkedIn)
Nichol Goldstein - Progress Community Manager
My name is Nichol Goldstein, a Progress Community Manager. If you've read even one post from me, you'll note I'm a lover of snark, sarcasm, and the bonds of the human experience, I've been connecting people with similar interests together for longer than I'll admit to being alive, am a member of the Community Roundtable, and lead a Progress Employee Resource Group for people with visible and invisible disabilities, Outside of the company, I have helped corporations earn awards for Public Community Service, owned businesses, spoken at conferences, and written/illustrated for comic books and novels.
(LinkedIn)
Grant Stowell - Domo Community Manager (AKA John Domo)
If you've been a part of the Community for a while, you may have seen my name come up once or twice! I have been with Domo for almost 4 years and have served the Community in some capacity for a good portion of that time. I started as a Community & Advocacy intern back in the heyday of 2023 where I first fell in love with this Community. Since then, I've jumped around in my responsibilities, including hosting Domo Boujee Bingo at Domopalooza, but it feels good coming full circle to work with this incredible Community again! I'm an actor at heart, having performed in dozens of short films, stage plays, and musicals. I was born on Saint Patrick's Day ☘️ (no, it hasn't made me any luckier), and I love to cook, game, and watch movies. (LinkedIn)
Q&A
While this change is exciting, I'm sure it also raises some questions. Below is a general Q&A, but please feel free to comment any of your questions below or DM them to me!
Why the change?
In case you didn't notice the logo looking a little different, Domo was acquired by Progress Software, and the transition is in full swing! I have had the privilege of getting to know members of the Progress team over the past few months and can ensure that the Community is in good hands. Progress cares deeply for their customers and has a thriving community of its own that Nichol runs!
What happened to Cam Barnes?
Our dear friend Cam was unfortunately let go during the transition and is no longer with Domo. We genuinely appreciate the time he dedicated to the Community and for his 11+ years of work at Domo. Cam is actively looking for his next role, so feel free to reach out to him on LinkedIn if you have any leads!
What does the Domo Community look like under Progress?
The Domo Community is already well established and will continue to operate as normal for the foreseeable future. With new chapters come new possibilities and as we continue learning from you over the coming months and years, we hope to evolve the Community into whatever its members need it to be!
Allocating Credits
Everyone in the company draws from one shared credit pool, and admins can’t enforce how much any department uses. Credit Utilization is a reporting view, and dataset frequency permissions only limit how often something runs, not what it costs.
We’d like the ability to:
- Allocate credits to departments or cost centers for the contract term
- Charge usage to the owner’s bucket
- Stop scheduled executions when a bucket runs out, until an admin reallocates credits
- Alert owners based on projected usage, so they know early if they’ll run out before renewal
Scenarios
- Build and forget. A use case that uses about 3,000 credits a year is built for one person. Later it’s no longer needed, but nobody deletes it because keeping it costs the owner nothing. We’re hesitant to automate cleanup, since one dataset could power 25 dataflows and hundreds of cards.
- Old lineages. We have dataflow lineages up to 10 levels deep that have run for years. Many could be consolidated, but the only time anyone reviews them is when I schedule a meeting to walk through each one.
- Limiting builders isn’t enough. We restricted building to about a dozen super users, but they still build every request without weighing the real value, and rarely delete anything.
- Cost lands on everyone. When someone builds for another team, the credits come from the shared pool, so the requester never weighs cost against value. Later there could be technical debt because no one deleted anything when the use case changed.
- Frequency permissions are limited. They limit how often a dataset runs, not what it costs, and they don’t cover storage, dataflows, workflows, or AI Pro. One large dataflow and five smaller ones can run on the same frequency and produce the same result, but the large one uses 1 credit and the five smaller ones use 5.
Linked Table - new column data type and control
Hi — just tried the Linked Table function in App Studio. I was able to create a linked table card with editable columns so users can add comments.
It would be great if the Domo team could consider adding the following features to make the Linked Table more practical for real use:
- Allow the card creator to hide the “Add column” (“+”) icon at the top right of the table, so users can update editable columns but cannot modify the table structure.
- In addition to Text, Date, and Calculated field types, add a dropdown field type to restrict users to pre-set options.
- Provide data validation settings to alert users when invalid values are entered.
- Add a column length limit setting for text fields, ideally with a visible remaining character counter.
Magic ETL - Freezing Tiles
Without knowing any of the technical realities here…Running preview over and over again from the very beginning seems really inefficient, and it would be great if we could "freeze" tiles up to a certain point to optimize preview time.
For all my fellow music producer hobbyists, there is a "freeze" in Logic Pro that allows users to consolidate individual tracks to audio in order to save CPU. I imagine this being similar to that feature in that the frozen tiles would be un-editable until you un-freeze them, but they would have the data already materialized from your last preview.
Change App Default for "Allow Editing in App Mode"
The default for text cards in an app (whether imported or newly added) is to "Allow Editing in App Mode" which allows any viewer of the app to click in and change the text of a text box.
This option can be individually unchecked for every text box in the app, but I'd love if there was a feature to change the default to not allow editing that could be controlled from the admin side, and we could opt into allowing editing rather than having to opt out
Add a Dynamic Transpose Tile to Magic ETL
my source data comes in with field headers in column 1 and all data elements in columns which vary in legth each refresh. Since I am unable to know ahead of time how many columns of data elements will exist within a given refresh, I am unable to use the megatable card or the dynamic unpivot tile options current at my disposal. If a Dynamic Transpose tile could be created within Magic ETL we could easily flip columns to rows resulting in the field headers received in column 1 now in row 1 and data elements receive in a varible quantity of columns now in rows as are needed to drive reporting from that dataset.
Table Colors: the most asked about feature since 2018 (and I can prove it)
Preamble
At Domopalooza, the first time (of several) I heard a new feature announced as "the most requested feature on the Domo community forum", I assumed it was the one I will propose. In fact, I hope to prove to you that this is the most requested feature, and the next time anyone tries to apply that title to a different feature, then I implore you to gently correct them that anything besides this feature can, at best, be the second-most requested feature.
For example, if someone says, "Announcing the GA release of the most requested feature in Domo! Dark Mode!"
You could say, "I hate to interrupt, but that is not the most requested feature."
The feature I am proposing gets asked about in different ways, but they all boil down to the same thing. Recently, there are some people that want to add scrolling to HTML tables, since they've been using HTML tags to apply conditional color formatting. The answer that gets is that the HTML table is about to be retired. That's fine, I don't like the HTML table, anyways. Other people request "conditional formatting" or "applying color rules based on a different column".
The way I would implement this is in the pivot table, which is way more flexible in handling data than the HTML table.
Proposal
In addition to Rows/Columns/Values, add an option for a "Series" or "Color" that could be used to apply color rules by cell, just like the "Series" in a bar graph.
Multiple Sync Schedules
It would be great if we could add multiple schedules for any dataset or Magic ETL. For example, being able to run a dataset every 30 minutes on Monday from 8am-11am, and then running one per day the rest of the week. Advanced scheduling doesn't allow for different times or different active hours on different days.
Reset Filters when Leaving the Drill-In View
Right now a user may drill into a Card with the following experience: The user selects a dimension value on the Card and is brought to a new Page that is filtered on the dimension value. However, when the user exits this drill-in view, the dimension value is still selected and filters the content on the original Page.
The idea: Create a way to configure the drill-in experience such that, when the user exists the drill-in view, the dimension value is NO LONGER selected and DOES NOT filter the content on the original Page.
Period Over Period Date Configurations as Controls on Dashboards
I would like to be able to add the "Date Range", "Graph by", and "Compare to" date elements to a dashboard as controls and be able to have it control a singular or specified card(s). If I have one period over period chart on a dashboard, my users have to use the page-level date configuration (where "Compare to" is only relevant for one card). That, or I need to create Variables, which negates the utility of the period over period chart
smaiolo





