Best Of
Release Notes: Knowledge Base Updates (v2.9.0)
Hello everyone!
We're excited to announce that version 2.9.0 of the Domo Documentation Hub is now available! This release is headlined by a significantly expanded MCP Server setup guide, two new connector articles, a developer API rebrand, and a major batch of new microlearning videos. You can view these changes in our knowledge base at www.domo.com/docs.
🌟 What's New
🤖 MCP Server: Full OAuth Setup Guide with Screenshots
The "Connect AI Tools to Domo Using MCP" article has been substantially expanded into a step-by-step OAuth setup guide. It now walks users through retrieving the MCP server URL from the AI Library, adding a custom connector in Claude Desktop, and authenticating with OAuth — with nine new screenshots illustrating each step. A new OAuth FAQ section covers common questions about domains, permissions, and troubleshooting. A post-connection capabilities section was also added to describe what users can do once connected.
Learn more about connecting AI tools to Domo using MCP.
🔌 New Connector Articles: Sansan and OpenAI Administration
Two new connector KB articles are now live. The Sansan Connector article covers connecting Domo to Sansan's business card management service via API key, including required grants, credential fields, and available reports. The OpenAI Administration Connector article explains how to pull OpenAI organization administration data — including audit logs, users, projects, API keys, usage, and costs — using an Admin API key with appropriate organization scopes.
See the new Sansan Connector and OpenAI Administration Connector articles.
📄 Documents API: Filesets Rebranded and Out of Beta
Both the Product API and App Framework API "Filesets" documentation have been renamed to Documents API and the Beta label has been removed, reflecting the feature's general availability and official branding. The navigation and internal cross-references have been updated to match.
See the updated Documents API (Product APIs) and Documents API (App Framework APIs).
🛠 Developer API Improvements
Three developer-facing articles received meaningful documentation improvements this release:
- AppDB API filter rules — A new warning block clarifies that all four core filter rule fields (
name,applyOn,applyTo,query) are required even when empty, and that omitting any of them causes the upload to fail. A minimal working example is now included alongside the explanation. Learn more in the AppDB API documentation. - Datasets API SQL restrictions — A new note on the query endpoint makes explicit that only read-only SELECT statements are supported, and that INSERT, UPDATE, DELETE, and MERGE statements will not execute. Users who need to ingest or update data are directed to the Streams API. See the Datasets API reference.
- Snowflake Key Pair Authentication — The public/private key pair setup section has been rewritten for clarity, with distinct sub-sections for generating unencrypted vs. encrypted private keys, cleaner command formatting, and a more logical step sequence. Read the updated Snowflake Key Pair Authentication Connector article.
📋 Connector Article Updates
Several existing connector articles received content additions and polish:
- Cvent REST Connector — A comprehensive reports reference table listing 60+ available reports (Air Actual, Attendees, Budget Items, Sessions, Speakers, Transactions, and more) was added to the Details pane documentation. See the updated Cvent REST Connector.
- SFTP Writeback Connector — The credential setup steps have been streamlined. The inline instructions for obtaining a Domo Client ID and Secret were replaced with a direct link to the canonical guide, reducing duplication and keeping the article easier to maintain.
- Minor link and text fixes were applied to the Gong, Azure DevOps, Asana, Conductor Searchlight, Vibe, Entrata, Shopify, Dataset via Email, Sage 300, Google BigQuery, and Facebook Advanced connector articles.
🎬 Domo Video Library — 13 New Microlearning Videos
The Domo Video Library has been updated with 13 new microlearning videos covering a wide range of platform topics, all added in June 2026:
- App Studio Overview
- Automate Magic ETL Dataflows Using Triggers and Schedules
- Create Custom Roles and Assign Grants in Domo
- Dashboards Overview
- Domo Everywhere: Embed Overview
- Domo Publish Overview
- Domo's Data Transformation Tools (4-part series: Overview, Magic ETL, Dataset Views, Beast Mode)
- Explore Data Integration Options in Domo
- Govern Data Access with Row- and Column-Based PDP
- Govern User Access in Domo with Roles, SSO, and Automation
- Magic ETL Dataflows: The History and Version Tabs
- Monitor Your Domo Instance with DomoStats
- Understanding Accounts for Secure Credential Storage and Sharing
- Understanding Domo's AI Architecture: From Models to Agentic Solutions
- Understanding Update Methods in Domo: Replace, Append, Upsert, and Partition
CURRENT_DATE reflective of instance time zone
Requesting CURRENT_DATE function in beastmode to be reflective of our company time zone instead of UTC. At 6pm daily (Central Time), our reporting is off as the UTC current date shifts to the next day. We were originally told this was a bug but after four months waiting for the fix, Support has come back saying this is functioning as intended. They are recommending we update all of our beastmodes (over 100 using this formula) to: DATE_ADD(CURRENT_DATE(), INTERVAL -5 HOUR) However, this does not take daylight savings time shifts into consideration. Requesting feature update to make CURRENT_DATE reflective of our company time settings.
Native Array Filtering in Analyzer
The Problem: To use an array/multi-value field (like tags) as a dashboard filter, we currently have to UNNEST the data in the ETL layer.
On large datasets (our base table is 8.7B rows / 8.5 TB), unnesting explodes the data size exponentially. This forces us to write heavy, complex windowed Beast Modes to avoid double-counting metrics, causing dashboards to take minutes to load.
The Request: Allow Analyzer to natively handle array fields for filtering.
- Drop an array field into the Filter bar, and let users multi-select individual elements.
- Under the hood, evaluate the filter as a
CONTAINSorARRAY_CONTAINSoperation, rather than a strict string match on the whole array.
The Benefit:
- Massive Performance: Eliminates the need to artificially duplicate billions of rows just for a filter.
- Simpler Math: We can use standard
SUMandAVGinstead of heavy window functions. - Storage Savings: Drastically reduces Domo storage footprints.
Report Builder Filters Carried Through When Linked Back
When you schedule an old dashboard as a report, the user can easily click on the report in the email and it takes them to the dash with the same filters. When you have an app and use Report Builder the best you can do is setup a button to take you back to the report without filters. I would like to have the defualt here to apply the same filters as those used when generating the report. I would suffice to have the ability to add a link of my own where I could include p_filters.
John689
Domo // Build - What can I present that is impactful to you?
I think everyone here knows about Domo // Build coming up on June 23rd. But if not - Here’s a link - go get registered and I'll wait for you here -
Ok - now that you are back I wanted to know what YOU want out of this? Here is the deal - I have 8 minutes. I'm not going to get into a code review session. But I also don't want to talk to developers like you don't know what AI is.
For what it is worth, I'm going to talk about a bit about a journey we have gone on with pricing and data validation and most importantly - automation. I want to share a few things we learned that aren't the normal technical things I see in sessions like this.
Keep it real - What can I present that is impactful to you? If it is nothing, just tell me, and I'll just do my best not to suck and be boring - but I make no promises.
SeanPT
Claude Connector for DOMO
Please add support for a Model Context Protocol (MCP) server integration, which would allow AI assistants like Claude to connect directly with Domo. MCP is an open standard developed by Anthropic that enables AI tools to interact with external platforms securely and efficiently
robynm
Return to active tab from Analyzer and on refresh
Whenever an app is refreshed or after exiting Analyzer the app always resets to the first tab. We use tabs a lot and can have many on a page. This behaviour is very frustrating, could this setting be changed to remember the previously active tab and return to that?
TC777
Build Pro Code Apps With Visual Studio and GitHub Actions
If you have been wanting to build pro code apps in Visual Studio and then publish them to Domo without having to use the Domo CLI, this video is for you.
In this video, I walk through how to develop an app in Visual Studio, create versions and branches with GitHub and then use the GitHub Actions feature to automate the publishing to Domo on every pull request.
Consolidate DomoStats "People" and Domo Governance "Users" datasets
There are two ways to pull a user list using the Domo connectors. The DomoStats "People" report has all the same columns as the Domo Governance "Users" report plus key additional columns like Employee ID and Department, but can only be scheduled to run once per day.
The Domo Governance "Users" has less columns and doesn't have all the key columns we need, but has the "advanced" scheduling options like hourly, every X hours, specific days, etc.
I'm using the Users dataset to drive a custom landing page with links to pages a user has access to based on profile/group, so being able to run the Users report several times per day is very useful to us to keep up with new user creation/access changes. However, I also use the "People" report because I need the additional fields for other purposes. It would be nice if the People report allowed for the advanced scheduling so we don't need to have two tables that are nearly identical.
ccccc4
Allow Groups as Owners of DataFlows
Today, groups cannot be assigned as the owner of any dataflows. This means, that any output of a given dataflow is by default set as the same owner. It also means that by default, error alerts are only sent to one person instead of a team.
We have a use case involving a development team who cannot be granted the manage datasets grant due to securiy permissions. Without that grant, they cannot see any datasets that are not in their name or assigned to a group they belong to. If one of these users creates a new output on an ETL they don't own, they will not be able to view the new output by default.
We'd like to be able to assign groups as owners of dataflows to alleviate these issues. It's already possible for datasets, so it makes sense to be added to flows as well.