Azure Blob Storage to Qlik Integration

How Datrise loads Azure Blob Storage into Qlik

Datrise syncs Azure Blob Storage's containers, blobs, blob metadata, snapshots, access tiers, and blob versions into Qlik as tables loaded into Qlik's associative engine (often via QVD). Flexible or custom fields land in flattened columns for the data model, and timestamps such as created, updated, and status changes are typed as date/time fields.

Sync is incremental: Datrise uses incremental QVD loads merged on stable id, so re-runs update only what changed. QVD files per entity and load date. Qlik's associative model joins on identically named fields, so Datrise standardizes key names so associations link correctly.

Ideal for associative, in-memory exploration in Qlik Sense.

Endpoints

Azure Blob Storage: Object storage for blobs and data lake files on Azure.

Qlik: Associative analytics with Qlik Sense apps and governed data models.

How Azure Blob Storage entities map to Qlik

Azure Blob Storage entity	Qlik object	Notes
containers	`azureblobstorage_containers`	id PK · custom fields → flattened columns for the data model
blobs	`azureblobstorage_blobs`	id PK · linked to azureblobstorage_containers
blob metadata	`azureblobstorage_blob_metadata`	id PK · linked to azureblobstorage_containers
snapshots	`azureblobstorage_snapshots`	id PK · linked to azureblobstorage_containers

FAQ

How does Datrise handle Azure Blob Storage's custom fields in Qlik?

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

How does the Azure Blob Storage to Qlik sync stay up to date?

It runs incrementally — Datrise uses incremental QVD loads merged on stable id.

Related pipelines

Early access

Connect Azure Blob Storage to Qlik 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.