DatriseAI-first ETL

Azure Table Storage GoodData

AI-first ETL from Azure Table Storage into GoodData. Governed entities, incremental sync, typed landing tables.

How Datrise loads Azure Table Storage into GoodData

Datrise syncs Azure Table Storage's records, events, and configuration objects 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

Azure Table Storage: SaaS or API data source for analytics and warehouse sync.

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

How Azure Table Storage entities map to GoodData

Azure Table Storage entityGoodData objectNotes
recordsazure_table_storage_recordsid PK · custom fields → flattened columns
eventsazure_table_storage_eventsdate dimensions events
configuration objectsazure_table_storage_configuration_objectsid PK · linked to azure_table_storage_records

FAQ

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

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

Related pipelines

Early access

Connect Azure Table Storage 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.