DatriseAI-first ETL

Datascope to Looker Integration

AI-first ETL from Datascope into Looker. Governed entities, incremental sync, typed landing tables.

How Datrise loads Datascope into Looker

Datrise syncs Datascope's forms, submissions, users, locations, attachments, and answers into Looker as governed warehouse tables with LookML-ready naming. Flexible or custom fields land in flattened columns (nested fields expanded for modeling), and timestamps such as created, updated, and status changes are typed as date/time dimension columns.

Sync is incremental: Datrise uses incremental refresh of the underlying warehouse tables Looker explores, so re-runs update only what changed. Date-partitioned fact tables for PDT performance. Looker models live in LookML on top of SQL, so Datrise lands clean, stable column names rather than churn that would break your views.

Ideal for governed, version-controlled BI on a warehouse.

Endpoints

Datascope: Mobile forms for field data capture.

Looker: Google Cloud BI with LookML semantic models and governed dashboards.

How Datascope entities map to Looker

Datascope entityLooker objectNotes
formsdatascope_formsid PK · custom fields → flattened columns (nested fields expanded for modeling)
submissionsdatascope_submissionsid PK · linked to datascope_forms
usersdatascope_usersid PK · linked to datascope_forms
locationsdatascope_locationsid PK · linked to datascope_forms

FAQ

How does Datrise handle Datascope's custom fields in Looker?

Flexible values are stored as flattened columns (nested fields expanded for modeling), so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Looker types.

How does the Datascope to Looker sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the underlying warehouse tables Looker explores.

Related pipelines

Early access

Connect Datascope to Looker 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.