QlikView - Lineage

This document outlines the lineage coverage, configuration requirements, metadata handling, supported scenarios, component behavior, transformation coverage, and known limitations for lineage extraction in QlikView. The QlikView connector provides production-ready lineage extraction across QlikView applications, QVD files, QVS scripts, SQL queries, LOAD statements, resident tables, dashboards, and visualizations. It supports both table-level and column-level lineage to provide visibility into data dependencies and transformations across QlikView workloads.

Lineage Configuration Requirements

Accurate lineage extraction depends on access to QlikView source files, execution logs, source database metadata, and supported SQL syntax. The required paths and source connections must be available before lineage generation.

Configuration Requirements Table

Configuration	Required Detail
Source Documents Path	The QlikView source document path must be configured using CONNECTION_ATTR_QV_SOURCEDOCUMENTSPATH
Execution Log Path	The QlikView execution log path must be configured using CONNECTION_ATTR_QV_LOGSPATH
Source Database Crawl	The source database crawl should be completed before the lineage build
Database Connection	Database connection information is required for source table resolution
File System Access	File system access is required for QVW, QVD, QVS files, and execution logs
SQL Dialect Support	Supported SQL dialects are required for SQL query parsing

Missing file system access, unavailable execution logs, incomplete source database metadata, or unsupported SQL syntax may result in incomplete lineage generation or source-target resolution.

Lineage Components

The QlikView connector supports lineage extraction across QlikView applications, scripts, data structures, and visualization components.

Component Support Matrix

Component / Feature	Availability
QVW Applications	✅
QVD Files	✅
QVS Scripts	✅
SQL SELECT Queries	✅
LOAD Statements	✅
Resident Tables	✅
Sheets	✅
Visualizations / Charts	✅
Dimensions	✅
Expressions	✅
Variables	⚠️
SET / LET Statements	⚠️
Calculated Fields	⚠️
CONCATENATE	⚠️
ApplyMap	⚠️
Binary Load	⚠️
AUTOGENERATE	⚠️
Inline Tables	✅
Excel/XLSX Sources	✅
Wildcard Columns (*)	✅
Set Analysis	⚠️
Dynamic Field Names	⚠️

The ⚠️ icon indicates partially supported functionality with limited lineage coverage in applicable scenarios.

Column Creation Support

The QlikView connector supports column-level lineage across direct mappings, aliases, resident tables, QVDs, wildcard columns, and supported transformations. Complex expressions and dynamically generated fields may provide partial or no column-level lineage.

Column Creation from Lineage

Transformation Type	Supported
Direct Column Mapping	✅
Alias Mapping (AS clauses)	✅
Wildcard Column Expansion (*)	✅
Resident Table Column Lineage	✅
QVD Column Lineage	✅
Expression-based Columns	⚠️
Calculated Fields	⚠️
Nested Functions	⚠️
Aggregate Expressions	⚠️
Dynamic Column Names	⚠️
Generated Fields (AUTOGENERATE)	❌
Set Analysis Expressions	⚠️

The ⚠️ icon indicates partially supported functionality with limited column-level lineage coverage in applicable scenarios.

Supported Use Cases

The QlikView connector supports lineage extraction across QlikView applications, source files, data loading operations, SQL queries, resident tables, and visualization components.

Supported Lineage Scenarios

Supported Scenario	Details
QVW → Database Lineage	Lineage from QlikView applications to source database tables
QVD → QVD Dependency Lineage	Lineage across dependent QVD files
Resident Table → Resident Table Lineage	Lineage across resident table transformations
SQL SELECT Query Lineage	Lineage from SQL SELECT queries to source objects
LOAD Statement Lineage	Lineage generated from supported QlikView LOAD statements
Excel/XLSX → QlikView Lineage	Lineage from Excel/XLSX sources into QlikView data structures
Inline Data → Resident Table Lineage	Lineage from inline data to resident tables
Store Statement Lineage	Lineage from resident tables to QVD files through Store statements
Column Alias Mapping	Column mapping through AS clauses
Dashboard → Sheet → Visualization Lineage	Lineage across QlikView dashboard, sheet, and visualization components
Dimension and Expression Lineage	Lineage for supported dimensions and expressions
Multi-layer Load → Transform → View Lineage	Lineage across multiple QlikView loading and transformation layers
Wildcard Column Expansion (*)	Expansion of wildcard columns for supported lineage scenarios
Column-level Lineage with Transformations	Column-level lineage across supported transformation patterns

Lineage extraction depends on available QlikView metadata, source files, execution logs, database metadata, and supported query and scripting syntax.

Partial or Limited Coverage

Certain QlikView scripting and transformation patterns provide partial lineage coverage. Limitations primarily apply to dynamic runtime behavior, complex expressions, lookup operations, and dependencies that cannot be resolved from available metadata or script definitions.

Scenarios

Scenarios	Limitation Description
Dynamic SQL and $(variable) Substitution	Complex nested variables may not fully resolve
Calculated Fields	Expressions are captured, but dependency resolution is partial
CONCATENATE Operations	Multiple source dependencies may not be fully linked
ApplyMap Lookups	Expressions are captured, but lookup lineage is not resolved
Set Analysis	Columns are extracted, but set expressions are ignored
Generated Fields (AUTOGENERATE)	The generated table is created without source lineage
Dynamic Field Names	Runtime-generated field names may not match crawled columns
Complex Resident Table Chains	Circular dependencies may not fully resolve
Binary Load	Lineage extraction is limited
Complex Nested Expressions	Column extraction is partial

Dynamic scripting, complex expressions, circular resident table dependencies, and runtime-generated metadata may result in incomplete lineage paths or reduced column-level lineage coverage.

Unsupported Scenarios

The connector does not provide complete lineage coverage for certain advanced QlikView scripting and runtime dependency patterns.

Unsupported Lineage

Not Supported	Impact	Workaround
Full Binary Load Lineage Across External QVW Applications	Complete lineage cannot be generated across external QVW application dependencies	Document the dependency separately
Complete Set Analysis Parsing and Dependency Tracking	Set expression dependencies are not fully captured	Use supported column-level lineage or document dependencies separately
Runtime-generated Dynamic Field Lineage	Runtime-generated fields cannot be reliably resolved against crawled metadata	Use statically defined fields where applicable
Advanced ApplyMap Dependency Resolution	Lookup source dependencies are not resolved in lineage	Document lookup dependencies separately
Full Dynamic SQL Parameter Resolution at Runtime	Runtime parameter values cannot be fully resolved	Use static SQL definitions where applicable
Complex Circular Resident Dependency Resolution	Complete dependency chains cannot be resolved	Simplify dependency chains where applicable
Complete CONCATENATE Lineage Across Multiple Dynamic Sources	Dynamic source relationships may not be fully established	Document source dependencies separately

Unsupported scenarios do not produce complete lineage and may appear disconnected in lineage visualization.

Current Functional Status

The QlikView connector provides strong lineage coverage across standard QlikView applications, QVD files, resident tables, SQL queries, dashboards, and visualizations. Table-level and column-level lineage are supported across common QlikView data loading and transformation patterns. Advanced scripting constructs and runtime-generated dependencies have partial or unsupported coverage.

Status Area	Details
Overall Coverage	Partial coverage across QlikView applications, QVD files, resident tables, SQL queries, dashboards, and visualizations
Lineage Depth	Strong table-level and column-level lineage for supported QlikView workloads
Supported Inputs	QVW applications, QVD files, QVS scripts, SQL queries, LOAD statements, Excel/XLSX sources, resident tables, and supported visualization components
Functional Scope	Lineage extraction across supported data loading, transformation, dependency, and visualization patterns
Column-level Coverage	Direct mappings, aliases, wildcard expansion, resident table columns, and QVD columns are supported
Limitation Areas	Dynamic SQL, complex expressions, Binary Load, ApplyMap, Set Analysis, CONCATENATE, dynamic field names, and circular resident dependencies
Resulting Output	Production-ready lineage for supported QlikView workloads with partial coverage for advanced scripting and runtime-dependent scenarios

The QlikView connector provides production-ready lineage across QlikView applications, QVD files, resident tables, SQL queries, dashboards, and visualizations, with strong column-level lineage support. Coverage remains partial for dynamic SQL resolution, complex expression parsing, Binary Load handling, and advanced QlikView scripting patterns.

---

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.