Best Of
Is the SQL Tile in Magic Broken?
I have seen multiple ETLs with SQL Tiles fail inexplicably with no changes to the ETL or underlying data. These ETLs have been running successfully for weeks or months. Is anyone else seeing this?
I first noticed this yesterday (6/15) around 3:40pm eastern
I have submitted a ticket, but I need to escalate here as this is base level functionality.
Re: April Community Forum Recap
He says he was hiding because he didn't want to surpass someone else on the all-time scoring list. ;)
Card Limitations
It has been 49 business days since @DavidChurchman posted what I consider the most significant forum discussion of 2026. And since then, I don't think a day has gone by where I don't realize I am limited by Domo cards.
The chart below is a mock-up. The numbers in the image are fake.
Challenge - can you replicate this with Domo cards - no blank bricks, no AI, as shown?
- Gauges are half circle, start at zero.
- Each gauge has a currency amount and a percent beneath it.
- Every slice (in the pie charts) show a label - even small slices
- Each pie chart has a total at the bottom and a legend on the side.
- Table chart has a horizontal bar on last column.
- Simply line chart with node (dot) at each reference point
Sample data would be something like
Fiscal Year | Category | Measure Type | Amount |
|---|---|---|---|
FY2025 | CAT1 | Budget | 35000000 |
FY2025 | CAT2 | Budget | 28000000 |
FY2025 | CAT3 | Budget | 24000000 |
FY2025 | CAT4 | Budget | 18000000 |
FY2025 | CAT5 | Budget | 15000000 |
FY2025 | CAT6 | Budget | 5000000 |
FY2025 | CAT1 | Actual | 12000000 |
FY2025 | CAT2 | Actual | 8000000 |
FY2025 | CAT3 | Actual | 24000000 |
FY2025 | CAT4 | Actual | 15000000 |
FY2025 | CAT5 | Actual | 3500000 |
FY2025 | CAT6 | Actual | 2300000 |
FY2025 | CAT1 | Remaining | 23000000 |
FY2025 | CAT2 | Remaining | 20000000 |
FY2025 | CAT3 | Remaining | 0 |
FY2025 | CAT4 | Remaining | 3000000 |
FY2025 | CAT5 | Remaining | 11500000 |
FY2025 | CAT6 | Remaining | 2700000 |
Re: April Community Forum Recap
Congrats to All!! Weird to see the leaderboard absent of our resident viking, @ArborRose ?!?
PDF Report Builder Beta: Pass a user-controlled filter to the report?
Has anyone figured out a way to pass the filter selections made by users on an App Studio page to the new PDF report? I like the ability to format the PDF, but ideally, I'd be able to have a user filter for the data they care about, and then use a button to "Export to PDF", which would then export the nicely formatted report for the data they care about. It's not practical or me to create a different view/button for every filter selection.
Re: Creating BM in View vs in Analyzer
As far as I know, they're identical. One difference in use is that in Views, you tend to be looking at the data by row, but in Analyzer, you tend to be aggregating the data. So something that looks like it's calculating correctly by row (in your view) might not calculate correctly by group (in analyzer).
See this post for a discussion of that issue:
Re: Reflections from Domopalooza 2026 and my Case for Cards
Terrific post @DavidChurchman.
Domo’s competitive advantage is making the data-to-dashboard workflow simple and accessible. Strategies that reinforce that strength will continue to add value; those that pull focus away from it risk diluting what makes Domo effective.
I agree that continued investment in the foundational layer—cards, data modeling, and overall usability—is critical. Personally, I’m not looking to use Domo for building workflows or writing code. If I need that, I can use tools like Claude or Cursor directly. It’s also worth considering the added cost implications when similar capabilities exist outside the platform.
It feels like some of the current direction is being influenced by executive demand to highlight how AI is being used, rather than how data is being effectively leveraged. In practice, I still see challenges with AI reliably handling even relatively simple data relationships, like joins across a few tables. That can lead to impressive demos, but inconsistent results in real-world use.
With that in mind—and acknowledging that some of these may already be in development or beta—here are a few suggestions focused on strengthening the core experience:
Cohort / Retention Card (simplified)
• A card that shows how groups of users behave over time after they start
Example:
Group users by when they signed up (e.g., January, February, March), then track what percentage of each group returns in later weeks or months
Signup Month | Week 1 | Week 2 | Week 3 |
|---|---|---|---|
Jan | 100% | 60% | 45% |
Feb | 100% | 55% | 40% |
Funnel / Conversion Card (simplified)
• A card that shows how people move through steps in a process—and where they drop off
Example (website flow):
Visited site → Signed up → Made a purchase
What you’d see:
Step 1: 10,000 users
Step 2: 4,000 users (40% conversion)
Step 3: 1,000 users (25% conversion from step 2)
Time Comparison Card (Smart)
• Automatically compares WoW, MoM, and YoY performance
• Includes % change and clear visual indicators
Variance / Waterfall Enhancements
• More robust variance analysis (plan vs. actual with contributing drivers)
• Moves beyond basic waterfall charts into clearer financial storytelling
Text / Narrative Card (non-AI)
• Rule-based summaries (not generative AI)
Example:
“Revenue increased 12% vs last month, driven by X”
Parameterized Cards
• A single card that can dynamically switch metrics or dimensions
• Reduces the need to duplicate multiple versions of the same card
Card-Level Versioning
• Track changes over time
• Ability to roll back when needed
Cross-Dataset Cards
• Blend data directly at the card level without requiring heavy ETL processes
Improved Debugging Tools
• Step-by-step data inspection
• Clearer error tracing and troubleshooting