DatriseAI-first ETL

Senseforce to GoodData Integration

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

How Datrise loads Senseforce into GoodData

Datrise syncs Senseforce's assets, sensor readings, events, machines, time series values, and alarms 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

Senseforce: Industrial IoT machine telemetry and analytics.

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

How Senseforce entities map to GoodData

Senseforce entityGoodData objectNotes
assetssenseforce_assetsid PK · custom fields → flattened columns
sensor readingssenseforce_sensor_readingsid PK · linked to senseforce_assets
eventssenseforce_eventsdate dimensions events
machinessenseforce_machinesid PK · linked to senseforce_assets

FAQ

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

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

Related pipelines

Early access

Connect Senseforce 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.