Workday → GoodData
AI-first ETL from Workday into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Workday into GoodData
Datrise syncs Workday's HR, finance entities, organizational structures, and operational events 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: Enterprise HR and finance source for operational reporting.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Workday entities map to GoodData
| Workday entity | GoodData object | Notes |
|---|---|---|
| HR | workday_hr | id PK · custom fields → flattened columns |
| finance entities | workday_finance_entities | id PK · linked to workday_hr |
| organizational structures | workday_organizational_structures | id PK · linked to workday_hr |
| operational events | workday_operational_events | date dimensions events |
FAQ
How does Datrise handle Workday'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 to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Workday
Early access
Connect Workday 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.