Gridly to MicroStrategy Integration

How Datrise loads Gridly into MicroStrategy

Datrise syncs Gridly's grids, records, columns, languages, views, and translation statuses into MicroStrategy as warehouse tables for MicroStrategy's schema objects. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the warehouse tables behind attributes and metrics, so re-runs update only what changed. Date-partitioned facts. MicroStrategy maps attributes to columns, so Datrise lands stable keys and names so metrics don't break.

Ideal for large-scale enterprise reporting and governance.

Endpoints

Gridly: Localization and content grids for games and apps.

MicroStrategy: Enterprise BI with dossiers, governed metrics, and mobility.

How Gridly entities map to MicroStrategy

Gridly entity	MicroStrategy object	Notes
grids	`gridly_grids`	id PK · custom fields → flattened columns
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 MicroStrategy?

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 MicroStrategy types.

How does the Gridly to MicroStrategy sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the warehouse tables behind attributes and metrics.

Related pipelines

Early access

Connect Gridly to MicroStrategy 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.