Amazon DynamoDB to Qlik Integration

How Datrise loads Amazon DynamoDB into Qlik

Datrise syncs Amazon DynamoDB's tables, items, partition keys, sort keys, attributes, and stream records 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

Amazon DynamoDB: Serverless key-value and document store on AWS.

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

How Amazon DynamoDB entities map to Qlik

Amazon DynamoDB entity	Qlik object	Notes
tables	`source_dynamodb_tables`	id PK · custom fields → flattened columns for the data model
items	`source_dynamodb_items`	id PK · linked to source_dynamodb_tables
partition keys	`source_dynamodb_partition_keys`	id PK · linked to source_dynamodb_tables
sort keys	`source_dynamodb_sort_keys`	id PK · linked to source_dynamodb_tables

FAQ

How does Datrise handle Amazon DynamoDB'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 Amazon DynamoDB to Qlik sync stay up to date?

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

Related pipelines

Early access

Connect Amazon DynamoDB 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.