DatriseAI-first ETL

Workday RaaS to GoodData Integration

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

How Datrise loads Workday RaaS into GoodData

Datrise syncs Workday RaaS's workers, organizations, job profiles, compensation records, absence records, and report rows 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

Workday RaaS: Workday HR reports delivered as a service.

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

How Workday RaaS entities map to GoodData

Workday RaaS entityGoodData objectNotes
workersworkday_raas_workersid PK · custom fields → flattened columns
organizationsworkday_raas_organizationsid PK · linked to workday_raas_workers
job profilesworkday_raas_job_profilesid PK · linked to workday_raas_workers
compensation recordsworkday_raas_compensation_recordsid PK · linked to workday_raas_workers

FAQ

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

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

Related pipelines

Early access

Connect Workday RaaS 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.