DatriseAI-first ETL

Excel File to GoodData Integration

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

How Datrise loads Excel File into GoodData

Datrise syncs Excel File's worksheets, rows, columns, headers, cell ranges, and workbooks 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

Excel File: Spreadsheet workbooks from exports and shared drives.

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

How Excel File entities map to GoodData

Excel File entityGoodData objectNotes
worksheetsexcel_file_worksheetsid PK · custom fields → flattened columns
rowsexcel_file_rowsid PK · linked to excel_file_worksheets
columnsexcel_file_columnsid PK · linked to excel_file_worksheets
headersexcel_file_headersid PK · linked to excel_file_worksheets

FAQ

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

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

Related pipelines

Early access

Connect Excel File 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.