DatriseAI-first ETL

Secoda to Tableau Integration

AI-first ETL from Secoda into Tableau. Governed entities, incremental sync, typed landing tables.

How Datrise loads Secoda into Tableau

Datrise syncs Secoda's tables, columns, dictionaries, lineage edges, owners, and documentation entries into Tableau as warehouse tables or a refreshed .hyper extract. Flexible or custom fields land in flattened columns for Tableau fields, and timestamps such as created, updated, and status changes are typed as date/datetime fields.

Sync is incremental: Datrise uses incremental refresh of the tables behind a live connection or extract, so re-runs update only what changed. Date-partitioned facts to keep extract refresh quick. Tableau .hyper extracts snapshot data, so Datrise keeps the source tables incremental and lets you choose live vs extract.

Ideal for visual analytics and dashboards in Tableau.

Endpoints

Secoda: Data catalog, lineage, and documentation.

Tableau: Salesforce analytics platform for interactive dashboards and visual exploration.

How Secoda entities map to Tableau

Secoda entityTableau objectNotes
tablessecoda_tablesid PK · custom fields → flattened columns for Tableau fields
columnssecoda_columnsid PK · linked to secoda_tables
dictionariessecoda_dictionariesid PK · linked to secoda_tables
lineage edgessecoda_lineage_edgesid PK · linked to secoda_tables

FAQ

How does Datrise handle Secoda's custom fields in Tableau?

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

How does the Secoda to Tableau sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the tables behind a live connection or extract.

Related pipelines

Early access

Connect Secoda to Tableau 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.