Best Of
Re: Inconsistent Interaction Filter Behavior
@ckwright, would know better than me, but I thought this would be true for the legend but not for the summary number. Not removing the legend of the card that you're clicking on makes some sense, because the legend can also be clicked on as an interactive filter, so it gives you another way to click/unclick the fields, and if it disappeared you would lose that ability.
But in my tests, the summary number is changed on both cards. I just posted some screengrabs on this other thread where that was true.
I tested a few other places and it seemed to be true where the summary number was changed on all cards, not just the non-clicked card.
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
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
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
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.
Drill in & interactive filtering at the same time?
I know there were some discussions about allowing users to have an ability to both drill in and filter other charts in the App, just want to know anyone has any update?
For example: I have a pie chart showing count of people by 'Active', 'Non-Active'.
Then add a drill path for this pie chart showing count of people by 'Non-Active < 7 days', 'Non-Active >= 7 days'.
So when I click on 'Non-Active' → it will drill into the 2nd pie chart, breaking down the Non-Active category for me.
But I have other charts in this App that I would like to also filtering to 'Non-Active' then to 'Non-Active >= 7 days'. Is this still unachievable?
App Theme: Changing App Color Pallete, color on charts still the same?
Edit App → App Theme → Edit Theme Colors → Chart colors section → I tried changing Chart color palette to a different one. But charts on my App still not changing color.
In Analyzer, these charts have no color rule applied or anything.
So how to I switch all the charts in my App to a different chart color palette?
Inheriting PDP policies for a given user when querying the dataset?
Hi,
So we're trying to build a user facing app that will be fed DOMO data. In particular its a chatbot that will be able to query and read in DOMO data for user insights and actionable recommendations.
The issue we're facing is, each of our users have particular data policies and these policies are encapsulated in a PDP that is attached to the dataset. When the user requests a view of the data we want that user to be able to only view data that is defined in these policies. The dataset api doesnt appear to restrict the view of the data per user via the parameters but rather when say the pydomo client is instantiated the views are inherited via whatever policy is attached to the client id and client secret.
Is there a way to get a user of our app to only see the data the would see in the DOMO dashboards? Or do we have to reimplement the PDPs on our backend?
Work Smarter, Not Harder - Introducing the Domo Toolkit Chrome Extension
Stop wasting time navigating menus, managing hundreds of identical browser tabs, copying dataset IDs from the URL, and constantly clearing your cookies.
Domo Toolkit is designed for the people who live inside Domo every day—administrators managing hundreds of objects, consultants jumping between client instances, and power users building on the platform. Every feature is built to save clicks, reduce context-switching, and surface information that Domo's native UI buries. Whether you're creating, updating, troubleshooting, auditing, or cleaning, Domo Toolkit puts the tools you need one click away.
Installation
Disclaimer
This extension is an independent, community-developed project. Domo, Inc. has no responsibility for its functionality or performance or for any consequences arising from its use.
Features
Context Detection
Automatically detects the Domo object you're viewing - pages, cards, datasets, dataflows, app studio pages, workflows, alerts, and 100+ other object types. The extension:
- Identifies the object and fetches metadata from the Domo API
- Detects card modals and resolves parent objects for nested types (e.g. app studio pages)
- Detects selected code engine and form actions inside workflow editors
- Updates the tab title with the object's name
- Provides one-click access to the object's full JSON definition, with epoch timestamps annotated as human-readable dates and user IDs annotated with display names
Automatic 431 Error Resolving
Handles Domo's "Request Header Fields Too Large" errors with three cookie clearing modes:
- Auto (default) - Detects 431 errors, clears cookies (preserving your last 2 active instances), and refreshes the page automatically
- Preserve - One-click clearing that keeps your last 2 instances
- All - Clears all Domo cookies while leaving other sites and history intact
One-Click Actions
- Copy ID - Copy the current object's ID. Long-press for related IDs like stream ID (datasets) or app ID (app studio pages). Keyboard shortcut:
Ctrl+Shift+1(Cmd+Shift+1on Mac). - Share With Self - Grant yourself access to pages, studio apps, and custom app designs.
- Activity Log - View activity log records for the current object. Long-press for advanced options: view activity for all cards on the current object, all pages containing those cards, or all child pages.
- Clipboard Navigation - Click this button to read your clipboard, identify the Domo object only by its ID on your clipboard, and navigate directly to it. Works with any Domo object ID copied from anywhere - a card, dataset, spreadsheet, Slack message, etc. For objects that don't support navigation, detailed information is displayed in the side panel instead.
- Delete Current Object - Delete beast modes, appdb collections, workflows, pages/app studio pages and all their cards, and dataflows and all their outputs. Includes confirmation dialog and child page safety checks.
Data Discovery
Opens in the side panel for persistent exploration without losing your place.
- Get Cards - Lists every card on a page, app studio page, worksheet page, report builder page, dataset, or dataflow outputs. For pages, forms and queues are included and separated from cards.
- Get Card Pages - Shows where cards on an object live. For pages, shows all other pages not including the current page that contain cards that also exist on the current page. For datasets and dataflows, shows all pages and app studio pages containing cards that use the dataset or dataflow outputs as a source.
- Get Child Pages - For pages, shows all child and grandchild pages.
- Get DataSets - Shows datasets for an object, including inputs and outputs datasets for dataflows, dependent views for datasets, and all datasets used in cards on a page or app.
- Get DataSets Used in View - For dataset views and datafusions, see the underlying source datasets that feed into the view.
All discovery lists support applicable actions like open all, copy ID, share with self, open lineage, open in views explorer, and remove from page. Items are grouped hierarchically or categorically with expand/collapse, counts, direct links, and IDs on hover.
Card Error Tracking
Card API errors are automatically captured as you browse. Click the Card Errors button to view them in the side panel with full response details. Errors are tracked per tab and cleared when you navigate away from a card. View error count at a glance, expand individual errors to see the full JSON response, and clear all errors with one click.
Object-Specific Actions
- Lineage - Open a full-page lineage graph for datasets and dataflows. Traces upstream and downstream dependencies with dataset previews and dataflow tile operations directly in the graph. Supports dark mode.
- Copy Filtered URL - Copy URL with all applied filters on a card, page, or app studio page (Pfilters).
- Export Data - Export card data in CSV or Excel format, including applied filters (can be done from a card modal!). Export code engine package versions as JavaScript/Python files.
- Data Repair - Open the hidden data repair tab for any dataset.
- Update Owner - Change ownership of alerts and workflows with a searchable user picker and a "Set to Self" shortcut.
- Update DataFlow Details - Edit a dataflow's name and description without creating a new version.
- Update Code Engine Versions - Bulk update workflow code engine actions to the latest version in a single click, without unmapping inputs and outputs.
- Lock Cards - Lock all cards on a page, app studio page, dataset, worksheet, report builder report, or all dataflow outputs.
- Set DataSet Schedule to Manual - Set a dataset's schedule to manual.
- Fix Empty String Filters - Remove empty string default values from "contains" quick filters on cards, so null values display when no value is entered instead of being filtered out.
Custom Favicons
Customize favicons per Domo instance using regex-based rules:
- Instance Logo - Use the instance's own logo as the favicon
- Colored Domo Logo - Custom background color on the Domo logo
- Colored Stripes - Add a colored stripe to the top, right, bottom, or left edge
- Regex Patterns - Match instance subdomains with flexible patterns
- Priority Ordering - Drag-and-drop rule ordering
Side Panel & Popup
- Popup - Click the extension icon for quick access
- Side Panel - Persistent panel alongside the page for data discovery, with collapsible actions. Opens automatically from the popup when displaying discovery results.
Both show the current context (instance, object type, object ID) and update as you navigate.
Settings
- Theme - System, light, or dark mode
- Default Domo Instance - Set your go-to instance for clipboard navigation from non-Domo sites
- Cookie Clearing Behavior - Choose between auto, preserve, or all modes
- Favicon Rules - Rule editor with pattern matching, effect selection, color picker, and drag-and-drop reordering
Supported Object Types
Pages, cards, datasets, dataflows, app studio apps (and their pages), worksheets (and their pages), workspaces, users, groups, alerts, workflows (including versions, executions, triggers, and actions), code engine packages (and versions), pro-code apps, beast modes, variables, access tokens, appdb collections, approvals, approval templates, jupyter workspaces, filesets, files, forms, governance toolkit jobs and dozens more.
Privacy
- Only runs on
.domo.comdomains - Uses Domo's existing authenticated session - no additional login required
- No data leaves the browser; no external servers are contacted
- Settings sync via Chrome's built-in storage
- Domo data is never read, stored, or sent off-device
See the full Privacy Policy for details.
Contributing
Interested in contributing? See CONTRIBUTING for the tech stack, architecture, development setup, code conventions, and key patterns.
Issues & Feedback
Found a bug or have a feature request? Open an issue.
brycec