DatriseAI-first ETL

SAP Fieldglass to GoodData Integration

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

How Datrise loads SAP Fieldglass into GoodData

Datrise syncs SAP Fieldglass's workers, job postings, work orders, time sheets, suppliers, and invoices 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

SAP Fieldglass: External workforce and contingent labor management.

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

How SAP Fieldglass entities map to GoodData

SAP Fieldglass entityGoodData objectNotes
workerssap_fieldglass_workersid PK · custom fields → flattened columns
job postingssap_fieldglass_job_postingsid PK · linked to sap_fieldglass_workers
work orderssap_fieldglass_work_ordersid PK · linked to sap_fieldglass_workers
time sheetssap_fieldglass_time_sheetsid PK · linked to sap_fieldglass_workers

FAQ

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

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

Related pipelines

Early access

Connect SAP Fieldglass 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.