Azure Table Storage to Yellowfin Integration

How Datrise loads Azure Table Storage into Yellowfin

Datrise syncs Azure Table Storage's tables, entities, partition keys, row keys, properties, and timestamps into Yellowfin as warehouse tables Yellowfin builds views on. 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 connected tables, so re-runs update only what changed. Date-partitioned facts. Yellowfin views reference columns by name, so Datrise lands stable, well-typed columns to keep reports valid.

Ideal for dashboards with automated data storytelling.

Endpoints

Azure Table Storage: Key-value NoSQL store on Azure.

Yellowfin: BI suite with dashboards, automated insights, and data storytelling.

How Azure Table Storage entities map to Yellowfin

Azure Table Storage entity	Yellowfin object	Notes
tables	`azure_table_storage_tables`	id PK · custom fields → flattened columns
entities	`azure_table_storage_entities`	id PK · linked to azure_table_storage_tables
partition keys	`azure_table_storage_partition_keys`	id PK · linked to azure_table_storage_tables
row keys	`azure_table_storage_row_keys`	id PK · linked to azure_table_storage_tables

FAQ

How does Datrise handle Azure Table Storage's custom fields in Yellowfin?

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

How does the Azure Table Storage to Yellowfin sync stay up to date?

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

Related pipelines

Early access

Connect Azure Table Storage to Yellowfin 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.