Best Of

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!