DatriseAI-first ETL

Oracle CX GoodData

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

How Datrise loads Oracle CX into GoodData

Datrise syncs Oracle CX's enterprise CX entities across sales, service, and customer operations 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

Oracle CX: Enterprise customer experience suite with sales and service data.

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

How Oracle CX entities map to GoodData

Oracle CX entityGoodData objectNotes
enterprise CX entities across salesoracle_cx_enterprise_cx_entities_across_salesid PK · custom fields → flattened columns
serviceoracle_cx_serviceid PK · linked to oracle_cx_enterprise_cx_entities_across_sales
customer operationsoracle_cx_customer_operationsid PK · linked to oracle_cx_enterprise_cx_entities_across_sales

FAQ

How does Datrise handle Oracle CX'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 Oracle CX to GoodData sync stay up to date?

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

Related pipelines

Early access

Connect Oracle CX 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.