Best Of
Release Notes: Knowledge Base Updates (v2.10.0)
Hello everyone!
We're excited to announce that version 2.10.0 of the Domo Documentation Hub is now available! This release brings expanded MCP connection guides, a new beta article on user impersonation, several new connector docs, and an important accuracy fix for the Databricks change-detection documentation. You can view these changes in our knowledge base at www.domo.com/docs.
🌟 What's New
🤖 Domo Essentials MCP: Expanded Connection Guides
The MCP documentation received a significant overhaul. The original single-page guide has been refactored into a focused hub that routes readers to dedicated articles based on how they want to connect. Two new how-to articles cover the two supported connection methods — standard OAuth and manual configuration — and two new reference articles clarify the distinction between agent knowledge types and between tools and skills. Read the updated Connect AI Tools to Domo Using MCP hub, or jump directly to connecting with Standard OAuth, connecting manually, agent knowledge vs. tool knowledge, or agent tools vs. agent skills.
🔌 New and Updated Connector Documentation
Three new connector articles are now live:
- Microsoft SharePoint — A step-by-step guide for connecting SharePoint documents to Domo using the SharePoint Online REST Enterprise OAuth connector. Learn more about connecting documents to Domo using Microsoft SharePoint.
- Cursor Administration — Documentation for importing team administration data (members, audit logs, usage, and costs) from Cursor into Domo. See the new Cursor Administration Connector article.
- Knack — Documentation for importing objects, field definitions, and records from Knack applications into a single Domo DataSet. See the new Knack Connector article.
Several existing connector articles also received reports table additions and minor field updates, including SurveyMonkey Advanced, ZiftOne, SAP Ariba, and multiple Microsoft SharePoint Online REST connector variants.
🔧 Databricks Change Detection: Accuracy Fix
The Domo on Databricks article contained an inaccurate description of how Domo detects DataSet updates. The article previously referenced a LAST_ALTERED timestamp; it now correctly describes the lastModified field returned by Databricks's DESCRIBE DETAIL command. A new FAQ note also clarifies that this check applies to tables only — Databricks views do not support it, so any DataFlow using a Databricks view is triggered on every freshness check cycle regardless of whether the underlying data changed. See the updated Domo on Databricks article.
🙏 Thank You
A heartfelt thank you to everyone who helped make this release possible. Your attention to accuracy and coverage makes the docs better for everyone.
If you have questions or feedback, please reach out — we're always happy to help!
Re: beastmode versus ETL formula - same formula, different result
In the BeastMode, when the value rounds to a whole number, it is passing that whole number (7) to the CONCAT with ".00" to get "7.00". The ETL is maintaining that decimal (7.0), probably because of how it deals with the 'float' data type, so it gets "7.0.00".
For both, I might try a different approach to get to the nearest quarter-hour that preserves the numeric data type.
Steps:
- Find time difference in decimal hours
- Multiply time diff by four
- Round to the ones place (no decimals)
- Divide by four.
- Round to the hundredths place (two decimals).
Example Calculation:
- 7:23 AM - 3:03 AM = 4.33 hours
- 4.33 * 4 = 17.32
- 17
- 17/4 = 4.25
- 4.25
Formula:
I haven't tested this, but I think this would work:
ROUND( ROUND( UNIX_TIMESTAMP(`TimeStamp_1`)-UNIX_TIMESTAMP(`TimeStamp_2`))/3600 * 4 ,0) / 4, 2)
Re: New Microlearning Video Resource Available
This is a gold mine, @zcameron! Thank you for sharing. Love to know what suggestions people add here for next videos!
Re: Hover Legend Average Basis
It does not look like it is possible for inside the donut. However, you could display it as the summary number. You would create a calculated field like this:
SUM(Cost) / SUM(Clicks)
and then choose that field in your summary number. In the summary number formatting options, choose to show two decimal places.
Re: Is the SQL Tile in Magic Broken?
Okay, thanks for that info. I have someone looking at it now.
Re: April Community Forum Recap
Unfortunately, that ignores @ggenovese achievement. Apologies, and belated congratulations to Giacome.
Re: Add Variable Linking to drop-down filter card
Update:
I looked again, and the "set variable" action now appears on all (most?) card types, not just the slicer. I tested it with the drop-down, and it worked. I tested it with a table, and it didn't, so not sure if that "set variable" action makes sense/should be on every card type, but I appreciate being on the drop-down card.
Re: Card Limitations
@ArborRose Thanks for posting, I love a good viz challenge!
I feel like I got pretty close to the mockups you shared, but you are correct I don't think these can be fully replicated in Domo pixel for pixel.
I do think the overall message/story can be replicated though, which in my opinion is the real purpose of a dashboard/visualizations.
These are all in the community instance if you want to take a look: https://domo-community.domo.com/page/479321682.
ellibot
Re: Card Limitations
I too think AI is overhyped. Especially if it's wrong. I can't get normal AI in Domo or outside to understand the joins between two or three tables. That said however, you definitely need to take a look at what can be done with Claude and Cursor for programming.
@Data_Devon isn't wrong. For programming inside or outside, it's a game changer. There are things AI can do well outside the hype. While I don't want AI inside my instance - I do use it to speed up my programming or do things like research information.
If my business were marketing or sales - sure, I'd find it much more useful. Because it can sort through information to find or summarized information very well.
Re: Workflow Error: `All shapes need to be connected to at least one other design element.`
@malina we'll need to take a closer look to determine why you are seeing this error. We would need your instance URL for the workflow which would include the model id and version. If you don't want to include those here, you can open a support ticket with those details.
