DatriseAI-first ETL

MongoDB Yellowfin

AI-first ETL from MongoDB into Yellowfin. Governed entities, incremental sync, typed landing tables.

How Datrise loads MongoDB into Yellowfin

Datrise syncs MongoDB's collections, documents, change streams, and schema snapshots into Yellowfin as warehouse tables Yellowfin builds views on. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. Yellowfin views reference columns by name, so Datrise lands stable, well-typed columns to keep reports valid.

Ideal for dashboards with automated data storytelling.

Endpoints

MongoDB: Document database often used as an operational source for analytics.

Yellowfin: BI suite with dashboards, automated insights, and data storytelling.

How MongoDB entities map to Yellowfin

MongoDB entityYellowfin objectNotes
collectionsmongodb_collectionsid PK · custom fields → flattened columns
documentsmongodb_documentsid PK · linked to mongodb_collections
change streamsmongodb_change_streamsdate/time dimensions events
schema snapshotsmongodb_schema_snapshotsid PK · linked to mongodb_collections

FAQ

How does Datrise handle MongoDB's custom fields in Yellowfin?

Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Yellowfin types.

How does the MongoDB to Yellowfin sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect MongoDB to Yellowfin the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.