Best Of
Horizontal tab placement flexibility
Whilst we have the option to place a tabbed section vertically anywhere on an app page there is no way, at present, to adjust the horizontal layout, the tabs always fit to the full page width so nothing can be added to the right or left of the tab area.
We have several use cases where we would like to have a fixed chart or control to the left of the tabs area rather than above it.
Is this possible to include in a future release please?
TC777
Show How Many Places a Card Exists Before Deleting
When deleting a card, it doesn't specify how many places the card exists. There's workarounds to look at this, but some of those workarounds only work if you have access to the other dashboards / apps to where the card exists. It would be good to give visibility to what the impact would be (even as simple as just a number of places the card exists) to expose to the user that is wanting to delete a card. This could decrease inadvertent impact from happening when deleting a card.
Variables Manager
Would be awesome to have a Variables Manager section (similar to Beast Mode Manager)
We are programmatically assigning variables and it's really hard to keep track of these, a dedicated management area would be very useful.
TC777
Run only when all input datasets have been updated
Please add a run trigger that will trigger only when ALL the input datasets I selected have been updated. That applies to both Magic ETL and Jupyter notebook.
Currently, when setting a run trigger and adding a condition to run when selected input datasets have been updated since the last successful run, the dataflow will run as soon as just one of the input dataset has been updated. The result is an incomplete input and therefore outdated output that is expected to be up to date. The workaround now is to use schedule instead if a schedule can be selected.
How can I add global variables to my AI Agents' instructions
I have several data retrieval agents which all need to use a base instructions across all of them, however, you cannot insert variables into instructions. This is an issue because we are just copy and pasting a large amount of the exact same text at the top of our agents instructions, going against coding DRY principals.
I have thought about a couple workarounds:
- Inserting into prompt
- having long prompts affects the output of the agent
- Using a file
- could reference a file within a fileset in the instruction
- however, clunky due to needing to be stored in a whole separate file
Is there something I am missing here?
Thanks
Enhance PDP to Allow SQL Filtering
PDP is currently limited and does not allow users to permission based on a condition in a given column/row.
Current State Example: The group that runs the farmers market can see the revenue that each vendor generated. Each vendor should be able to see the quantity sold for all farmers market sales, but they're not entitled to see revenue or which vendors benefited from a particular sale, except their own. Each vendor is allowed to see their own quantity sold and the total sold quantity for any items they sale.
There needs to be a way to apply conditional PDP for individual intersection masking. Users should be allowed to add SQL statements that cross-reference row level governance. Sara can only see the value in the column Vendor, Unit Price, and Revenue Generated if a certain criteria is met within the row of the vendor column. Simply filtering out the rows doesn't work for Sara because she needs to see the total market possible at the farmers market to aid in her production decisions for the upcoming harvest.
New Microlearning Video Resource Available
Introducing the Domo Video Library: Short Videos, Real Answers
We're excited to share something new with the Domo community: the Domo Video Library, a free microlearning video library built to help you get more out of Domo, faster. And we're letting Domo Community members in on it early.
What Is It?
The Video Library is a growing collection of short videos covering Domo features, workflows, and use cases. Content is contributed by Domo product managers, solution experts, and other Domo team members who know the platform inside and out. Videos are focused and to the point, generally under 10 minutes and often closer to 3, so you can find what you need and get back to work.
As a bonus, the Video Library was built as a Domo app using Domo tools. It is made available to you publicly through our Domo Everywhere tools.
How to Use It
Browse or search the library to find videos on topics relevant to you. Each video has a Share button that generates a direct link you can share with a teammate. No login required. Here's the link: https://embed.domo.com/cards/2W9VW
Visit the Domo Public Video Library
What's Coming
We'll be adding new videos on a regular basis, covering more features, use cases, and how-to content as the library grows. This is just the beginning.
Suggestions Welcome
You know better than anyone what you wish you had a quick video for. If there's a topic, feature, or workflow you'd love to see covered, post your suggestion right here in the comments. We'll use community feedback to help shape what gets added next.
We hope this microlearning library becomes a resource you leverage often.
zcameron
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.


