DatriseAI-first ETL

Orbit Love GoodData

AI-first ETL from Orbit Love into GoodData. Governed entities, incremental sync, typed landing tables.

How Datrise loads Orbit Love into GoodData

Datrise syncs Orbit Love's records, events, and configuration objects into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.

Ideal for embedded, multi-tenant analytics.

Endpoints

Orbit Love: SaaS or API data source for analytics and warehouse sync.

GoodData: Composable analytics platform with headless BI and embedded dashboards.

How Orbit Love entities map to GoodData

Orbit Love entityGoodData objectNotes
recordsorbit_love_recordsid PK · custom fields → flattened columns
eventsorbit_love_eventsdate dimensions events
configuration objectsorbit_love_configuration_objectsid PK · linked to orbit_love_records

FAQ

How does Datrise handle Orbit Love's custom fields in GoodData?

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 GoodData types.

How does the Orbit Love to GoodData sync stay up to date?

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

Related pipelines

Early access

Connect Orbit Love to GoodData 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.