data-upload-java-cli
Domo Data Upload Guide
Preferred Strategy — JSON Connector first, CLI fallback: When the data source is a REST/JSON API, always try the Domo JSON No-Code Connector (
domo-json-no-code-connectorskill) first. It creates a live, re-runnable connector stream inside Domo so data can be refreshed from the UI without re-running scripts. Only fall back to the Java CLI when:
- The JSON connector fails (auth issues, unsupported pagination, parsing errors), or
- The data is already in CSV form (local files, database exports, etc.) and there is no source API to connect to.
Overview
This guide covers the Java CLI fallback for uploading CSV data to Domo using domoutil.jar. The CLI handles schema derivation, dataset creation, chunked uploads, and indexing automatically.
JSON Connector First / CLI Fallback Pattern
When pulling from a REST/JSON API into Domo, use this two-path strategy in code:
def ingest_object(obj_type, cfg):
More from stahura/domo-ai-vibe-rules
migrate-lovable
Convert SSR-heavy Lovable/v0 apps into client-only Domo apps.
61domo-js
Use ryuu.js (domo.js) APIs for env, events, navigation, and data calls.
60appdb
Toolkit-first AppDB document CRUD, query operators, and collection wiring.
58html-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.
58data-api
High-level entry skill for Domo data access. Routes detailed query work to dataset-query.
57jsapi-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).
57