Rki Covid → GoodData
AI-first ETL from Rki Covid into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Rki Covid into GoodData
Datrise syncs Rki Covid'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
Rki Covid: SaaS or API data source for analytics and warehouse sync.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Rki Covid entities map to GoodData
| Rki Covid entity | GoodData object | Notes |
|---|---|---|
| records | rki_covid_records | id PK · custom fields → flattened columns |
| events | rki_covid_events | date dimensions events |
| configuration objects | rki_covid_configuration_objects | id PK · linked to rki_covid_records |
FAQ
How does Datrise handle Rki Covid'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 Rki Covid to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Rki Covid
Early access
Connect Rki Covid 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.