> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release7.2/connectors/connector-repositories/reporting-tool/qlikview/qlikview-lineage.md).

# 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

<table data-search="false"><thead><tr><th width="226.0078125">Configuration</th><th width="539.09375">Required Detail</th></tr></thead><tbody><tr><td>Source Documents Path</td><td>The QlikView source document path must be configured using <code>CONNECTION_ATTR_QV_SOURCEDOCUMENTSPATH</code></td></tr><tr><td>Execution Log Path</td><td>The QlikView execution log path must be configured using <code>CONNECTION_ATTR_QV_LOGSPATH</code></td></tr><tr><td>Source Database Crawl</td><td>The source database crawl should be completed before the lineage build</td></tr><tr><td>Database Connection</td><td>Database connection information is required for source table resolution</td></tr><tr><td>File System Access</td><td>File system access is required for QVW, QVD, QVS files, and execution logs</td></tr><tr><td>SQL Dialect Support</td><td>Supported SQL dialects are required for SQL query parsing</td></tr></tbody></table>

{% hint style="warning" %}
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.
{% endhint %}

## Lineage Components

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

### Component Support Matrix

<table data-search="false"><thead><tr><th>Component / Feature</th><th align="center">Availability</th></tr></thead><tbody><tr><td>QVW Applications</td><td align="center">✅</td></tr><tr><td>QVD Files</td><td align="center">✅</td></tr><tr><td>QVS Scripts</td><td align="center">✅</td></tr><tr><td>SQL SELECT Queries</td><td align="center">✅</td></tr><tr><td>LOAD Statements</td><td align="center">✅</td></tr><tr><td>Resident Tables</td><td align="center">✅</td></tr><tr><td>Sheets</td><td align="center">✅</td></tr><tr><td>Visualizations / Charts</td><td align="center">✅</td></tr><tr><td>Dimensions</td><td align="center">✅</td></tr><tr><td>Expressions</td><td align="center">✅</td></tr><tr><td>Variables</td><td align="center">⚠️</td></tr><tr><td>SET / LET Statements</td><td align="center">⚠️</td></tr><tr><td>Calculated Fields</td><td align="center">⚠️</td></tr><tr><td>CONCATENATE</td><td align="center">⚠️</td></tr><tr><td>ApplyMap</td><td align="center">⚠️</td></tr><tr><td>Binary Load</td><td align="center">⚠️</td></tr><tr><td>AUTOGENERATE</td><td align="center">⚠️</td></tr><tr><td>Inline Tables</td><td align="center">✅</td></tr><tr><td>Excel/XLSX Sources</td><td align="center">✅</td></tr><tr><td>Wildcard Columns (<code>*</code>)</td><td align="center">✅</td></tr><tr><td>Set Analysis</td><td align="center">⚠️</td></tr><tr><td>Dynamic Field Names</td><td align="center">⚠️</td></tr></tbody></table>

{% hint style="info" %}
The ⚠️ icon indicates partially supported functionality with limited lineage coverage in applicable scenarios.
{% endhint %}

## 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

<table data-search="false"><thead><tr><th>Transformation Type</th><th align="center">Supported</th></tr></thead><tbody><tr><td>Direct Column Mapping</td><td align="center">✅</td></tr><tr><td>Alias Mapping (<code>AS</code> clauses)</td><td align="center">✅</td></tr><tr><td>Wildcard Column Expansion (<code>*</code>)</td><td align="center">✅</td></tr><tr><td>Resident Table Column Lineage</td><td align="center">✅</td></tr><tr><td>QVD Column Lineage</td><td align="center">✅</td></tr><tr><td>Expression-based Columns</td><td align="center">⚠️</td></tr><tr><td>Calculated Fields</td><td align="center">⚠️</td></tr><tr><td>Nested Functions</td><td align="center">⚠️</td></tr><tr><td>Aggregate Expressions</td><td align="center">⚠️</td></tr><tr><td>Dynamic Column Names</td><td align="center">⚠️</td></tr><tr><td>Generated Fields (<code>AUTOGENERATE</code>)</td><td align="center">❌</td></tr><tr><td>Set Analysis Expressions</td><td align="center">⚠️</td></tr></tbody></table>

{% hint style="info" %}
The ⚠️ icon indicates partially supported functionality with limited column-level lineage coverage in applicable scenarios.
{% endhint %}

## 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

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

{% hint style="info" %}
Lineage extraction depends on available QlikView metadata, source files, execution logs, database metadata, and supported query and scripting syntax.
{% endhint %}

## 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

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

{% hint style="warning" %}
Dynamic scripting, complex expressions, circular resident table dependencies, and runtime-generated metadata may result in incomplete lineage paths or reduced column-level lineage coverage.
{% endhint %}

## Unsupported Scenarios

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

### Unsupported Lineage

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

{% hint style="info" %}
Unsupported scenarios do not produce complete lineage and may appear disconnected in lineage visualization.
{% endhint %}

## 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.

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

{% hint style="info" %}
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.
{% endhint %}

***

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release7.2/connectors/connector-repositories/reporting-tool/qlikview/qlikview-lineage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.