DatriseAI-first ETL

Sap Fieldglass Metabase

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

How Datrise loads Sap Fieldglass into Metabase

Datrise syncs Sap Fieldglass's records, events, and configuration objects into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.

Ideal for self-serve questions and dashboards for whole teams.

Endpoints

Sap Fieldglass: SaaS or API data source for analytics and warehouse sync.

Metabase: Open-source analytics with questions, dashboards, and embedded insights.

How Sap Fieldglass entities map to Metabase

Sap Fieldglass entityMetabase objectNotes
recordssap_fieldglass_recordsid PK · custom fields → flattened columns for the question builder
eventssap_fieldglass_eventstemporal columns for trends events
configuration objectssap_fieldglass_configuration_objectsid PK · linked to sap_fieldglass_records

FAQ

How does Datrise handle Sap Fieldglass's custom fields in Metabase?

Flexible values are stored as flattened columns for the question builder, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Metabase types.

How does the Sap Fieldglass to Metabase sync stay up to date?

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

Related pipelines

Early access

Connect Sap Fieldglass to Metabase 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.