Community
Forums
Forums
Ask questions, help other users, get involved.
New to Community
Take full advantage of all the forum has to offer.
Categories
Browse discussions by category.
Ideas Exchange
Help shape Domo by sharing your product ideas.
spacer
Events & Meetups
Network and swap stories at virtual & hybrid events.
Domo Ovation Awards
See how community members rock their Domo.
Domo For Good
Help a non-profit with a meaningful data project.
Help
Getting Started
Help Overview
Get answers on how to use or troubleshoot Domo.
Get started
Here's what you need to know to start using Domo.
Data Creators & Analysts
Learn to analyze data and create reports for others.
Data Consumers
Learn to create, view, and interact with data.
Data Engineers
Learn to integrate, govern, and build data assets.
Knowledge Base
How-To-Articles
Get detailed instructions about how to use Domo.
Release Notes
Stay current with new product enhancements.
How-To-Videos
See how to complete key tasks with Domo.
Support
Get product assistance from Domo Support.
University
Self-paced Training
Get on-demand eLearning modules for your role.
Virtual Training
Get remote live training in a public or private class.
In-person Training
Book a trainer to come get the team up to speed.
Certifications
Get Domo certified and build your resume.
Developer
Get Started
Start your free trial to start developing on Domo.
Docs & APIs
Use Domo to connect, process, and access data at scale.
Manage Client IDs
Log in to manage client IDs
Domo.com
Support
Home
›
JohnKalan_HITRUST
›
Comments
JohnKalan_HITRUST
Member
Activity
Posts
2
Comments
1
Comments
Thank you for the excellent summary. Domo support has indicated that is not possible to prevent the query and that we should add resources. We have reconsidered the need for the card and dataset and removed them.
in
Federated dataset: can I prevent a non-filtered preemptive query?
Comment by
JohnKalan_HITRUST
May 6
Activity
Posts
2
Comments
1
