Gridly to Tableau Integration

How Datrise loads Gridly into Tableau

Datrise syncs Gridly's grids, records, columns, languages, views, and translation statuses 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

Gridly: Localization and content grids for games and apps.

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

How Gridly entities map to Tableau

Gridly entity	Tableau object	Notes
grids	`gridly_grids`	id PK · custom fields → flattened columns for Tableau fields
records	`gridly_records`	id PK · linked to gridly_grids
columns	`gridly_columns`	id PK · linked to gridly_grids
languages	`gridly_languages`	id PK · linked to gridly_grids

FAQ

How does Datrise handle Gridly'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 Gridly 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 Gridly 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.