DatriseAI-first ETL

Google Cloud Storage F GoodData

AI-first ETL from Google Cloud Storage F into GoodData. Governed entities, incremental sync, typed landing tables.

How Datrise loads Google Cloud Storage F into GoodData

Datrise syncs Google Cloud Storage F'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

Google Cloud Storage F: SaaS or API data source for analytics and warehouse sync.

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

How Google Cloud Storage F entities map to GoodData

Google Cloud Storage F entityGoodData objectNotes
recordsgoogle_cloud_storage_f_recordsid PK · custom fields → flattened columns
eventsgoogle_cloud_storage_f_eventsdate dimensions events
configuration objectsgoogle_cloud_storage_f_configuration_objectsid PK · linked to google_cloud_storage_f_records

FAQ

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

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

Related pipelines

Early access

Connect Google Cloud Storage F 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.