BI & Analytics connector

The Qlik data catalog your whole team can trust.

The Dawiso Qlik connector turns your tenant into a searchable data catalog: every app, sheet, measure and load script, with the data connections each app relies on.

Read the docs

Live connector Stable connector

Qlik

Dawiso

Metadata-only · your data never leaves the source

Type: BI & data integration platform
Auth: API key (custom role)
Sync: Scheduled, incremental
Direction: Read-only · metadata

First things first

What is a data connector?

Metadata-only Read-only access Incremental sync Cross-system lineage

A data connector is the bridge between a tool in your stack and the catalog that gives you a unified view of it. Once a connector is configured, it reaches into the source system on a schedule, reads out the metadata - schemas, tables, dashboards, jobs, ownership, lineage - and represents it inside the catalog. Your actual rows and values stay where they are.

Connectors are the reason a data catalog can answer questions like "which Power BI dashboard depends on this Snowflake table?" or "who owns the orders topic in Kafka?" - automatically, without anyone keeping a spreadsheet up to date.

Three properties separate a good connector from a brittle one: it should be read-only and safe, it should be incremental so a full re-scan isn't required for every refresh, and it should resolve lineage across system boundaries, not just inside one tool.

About the platform

What is Qlik?

Qlik is a Swedish-founded BI and data integration platform that ships in two flavours: Qlik Cloud (SaaS) and Qlik Sense Enterprise on-premises. Manufacturers, energy companies and retailers use it to build associative dashboards on top of warehouses and operational systems.

Qlik Catalog (formerly Talend Data Catalog) covers what Qlik sells. What it doesn't cover is the rest of your estate: the warehouse the app loads from, the data product the business owns, the shared glossary, and the policy that rides along. That's where the Dawiso Qlik data catalog joins the picture: read-only, metadata-only, and cross-platform.

Architecture

How Dawiso connects to Qlik

A small read-only role on the Qlik side. The Dawiso scanner pulls metadata on a schedule. Everything ends up in your catalog, business-readable.

Source

Qlik Cloud / Qlik Sense Enterprise

Spaces & apps
Sheets & visualizations
Master items & load scripts
Data connections

REST · JDBC

Dawiso scanner

Read-only metadata

Schema & object discovery
Dependency resolution
SQL flow parsing (optional)
Sampling on opt-in

Internal

Catalog

Dawiso platform

Searchable metadata
Lineage & ownership
Business glossary
Policy & classifications

Connection details

Protocol: Qlik REST API + QRS API (on-prem)
Authentication: API key bound to a non-tenant user with custom role
Lineage: App-to-sheet-to-data-connection relationships resolved from app metadata, so each app is catalogued with the data connections it relies on

Setup

Connect Qlik in 4 steps

01

Create a custom role

In Qlik Cloud Administration, create a role (e.g. Dawiso Integration) with the Manage API keys permission, then assign it to a non-tenant user. Tenant admins cannot generate keys.
02

Generate an API key

Signed in as the non-tenant user, open API Keys in Administration and generate a new key. Copy the token; it is shown only once.
03

Connect in Dawiso

Add the Qlik host (tenant.region.qlikcloud.com or your on-prem server). Paste the API key. On-prem deployments add the proxy host and port.
04

Pick apps and scan

Provide a comma-separated list of App IDs to ingest. Schedule incremental ingestion to keep apps, sheets and their data connections current.

Capabilities

What you get with the Qlik connector

App & sheet catalog

Every Qlik app, sheet and visualization across your tenant is searchable, with thumbnails, owners and the space it belongs to.
App & data connection relationships

See which apps and sheets rely on which data connections, resolved from app metadata, so dependencies are clear before you change anything.
Master measure library

Centralize master measures, dimensions and load-script expressions so the same revenue formula is not redefined in dozens of apps.
Usage & adoption

See which apps get opened, which gather dust, and who the power users are. Retire what nobody opens with evidence.
Ownership & certification

Mark apps as certified, deprecated or under review. The owner is visible directly in the catalog alongside Qlik space permissions.
Both deployments covered

One connector for Qlik Cloud and Qlik Sense Enterprise on-premises, so a mixed estate ends up in a single governed catalog.

Business value

Why teams turn on the Qlik connector

−65%
Fewer duplicate apps

Business users find the certified app in Dawiso instead of asking three teams whether the new sheet should replace the old one.
10×
Faster impact analysis

Before retiring a data connection, see exactly which Qlik apps, sheets and master measures rely on it. Seconds, not days.
Production
Used at Olvi & Fortum

Qlik Enterprise and Qlik Cloud scanners are deployed at customers including Olvi and Fortum, alongside their other Dawiso connectors.

Ready to catalog your Qlik?

Set up the connector in an afternoon. See your first lineage graph the same day.

Read the docs

Frequently asked questions

Still curious? Talk to our team ->

What is Qlik data catalog?

Qlik offers Qlik Catalog (and Talend Data Catalog) within its ecosystem. Dawiso is cross-platform: it reads Qlik app and data metadata read-only and catalogs it alongside warehouses and other BI with a shared business glossary and the data connections each app relies on.

Does Qlik have a data catalog?

Yes, within its ecosystem. Dawiso adds the cross-platform layer: it catalogs Qlik apps, sheets and their data connections and places them alongside the rest of your stack in one searchable catalog.

What is a data catalog used for?

A data catalog makes every Qlik app and dataset discoverable, documented and trustworthy. Dawiso catalogs Qlik content with the data connections it relies on for the whole business.

What permissions does Dawiso need in Qlik?

A non-tenant user assigned a custom role with the Manage API keys permission, plus an API key bound to that user. Dawiso never modifies apps or data; the integration is read-only.

Does Dawiso copy Qlik app data?

No. Dawiso queries the Qlik REST API (or QRS API on-prem) for metadata only. App rows and chart values stay inside Qlik. Sampling and profiling are opt-in per data source.

Are both Qlik Cloud and Qlik Sense Enterprise supported?

Yes. Qlik Cloud uses the tenant URL and a Qlik Cloud API key. Qlik Sense Enterprise on-premises uses the server hostname plus optional proxy host and port. Same connector, same catalog.

Which Qlik objects end up in the catalog?

Tenants and spaces, apps and sheets, master measures and dimensions, load scripts, data connections, variables, bookmarks, and users with their permissions. App IDs are listed comma-separated at ingestion time.