programmatic-filters
Domo Programmatic Filtering
Control what data each viewer sees in embedded Domo content via server-side filters and dataset switching. Enforced by Domo — end users can't bypass. For client-side filtering, see jsapi-filters.
How It Works
A proxy user (service account) acts on behalf of all viewers. Your server:
- Authenticates with Domo (OAuth client credentials → access token)
- Requests an embed token with viewer-specific filters
- Returns the token to the client, which POSTs it to an iframe
Prerequisites
- Domo API client with
CLIENT_IDandCLIENT_SECRET(developer.domo.com > My Account > New Client) - Embed ID (5-char ID from the embed dialog, not the page URL)
- Dataset column names/IDs for filtering
All auth must happen server-side (CORS restrictions). Never expose credentials client-side.
More from stahura/domo-ai-vibe-rules
migrate-lovable
Convert SSR-heavy Lovable/v0 apps into client-only Domo apps.
60domo-js
Use ryuu.js (domo.js) APIs for env, events, navigation, and data calls.
59appdb
Toolkit-first AppDB document CRUD, query operators, and collection wiring.
57html-deck
Build a professional HTML slide deck from source content and convert it to a pixel-perfect PDF. Covers slide architecture, layout patterns, print-safe CSS, Puppeteer PDF conversion, and quality verification. Use when creating presentation decks, converting documents to slide format, or generating PDF decks from HTML.
57data-api
High-level entry skill for Domo data access. Routes detailed query work to dataset-query.
56jsapi-filters
Apply runtime filters to embedded Domo dashboards/cards from the host page via the JS API (MessagePort). Covers dynamic filtering, drill events, filter change listeners, iframe resize, pfilter URL params, overrideFilters, and App Studio appData. Use for any client-side Domo embed interaction. Not for server-side programmatic filters (use programmatic-filters).
56