> 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/release8.2/connectors/connector-repositories/reporting-tool/qlikview.md).

# QlikView

This article outlines the integration with the QlikView connector, enabling streamlined metadata management through features such as crawling and lineage building (Automatic and Manual). The connector extracts metadata from QlikView applications, sheets, report fields, variables, and source code, providing comprehensive visibility into reporting assets and their relationships.
\
The connector establishes connectivity through a Network File System (NFS) by accessing QVS and QVW files from the configured source documents path. Authentication is based on a QlikView service account with the required permissions to access the QVS and QVW file locations for connector validation, metadata crawling, lineage extraction, and related operations.

<img src="/files/IxMNTWFWtZ1QBtyqYHGH" alt="" height="311" width="624">

## Overview

### Connector Details

| Connector Category                                                           | Reporting Tools        |
| ---------------------------------------------------------------------------- | ---------------------- |
| OvalEdge Release Supported                                                   | Release6.3.4 and later |
| <p>Connectivity</p><p>\[How the connection is established with QlikView]</p> | NFS                    |
| Verified QlikView Version                                                    | Version 12.100         |

{% hint style="info" %}
The QlikView connector validates with the listed “Verified QlikView Version” and supports other compatible QlikView versions. If there are any issues with validation or metadata crawling, please submit a support ticket for investigation and feedback.
{% endhint %}

### Connector Features

<table data-search="false"><thead><tr><th>Feature</th><th align="center">Availability</th></tr></thead><tbody><tr><td>Crawling</td><td align="center">✅</td></tr><tr><td>Profiling</td><td align="center">NA</td></tr><tr><td>Query Sheet</td><td align="center">NA</td></tr><tr><td>Report Preview</td><td align="center">❌</td></tr><tr><td>Auto Lineage</td><td align="center">✅</td></tr><tr><td>Manual Lineage</td><td align="center">✅</td></tr><tr><td>Secure Authentication via Credential Manager</td><td align="center">✅</td></tr><tr><td>Data Quality</td><td align="center">NA</td></tr><tr><td>DAM (Data Access Management)</td><td align="center">NA</td></tr><tr><td>Bridge</td><td align="center">✅</td></tr></tbody></table>

{% hint style="info" %}
'NA' indicates that the respective feature is 'Not Applicable.'
{% endhint %}

### Metadata Mapping

The following objects are crawled from QlikView and mapped to the corresponding UI assets.

<table data-search="false"><thead><tr><th width="130">QlikView Object</th><th>QlikView Attribute</th><th>OvalEdge Attribute</th><th>OvalEdge Category</th><th>OvalEdge Type</th></tr></thead><tbody><tr><td>Streams</td><td>Stream</td><td>Report Group</td><td>Report Group</td><td>Domain</td></tr><tr><td>Apps</td><td>App</td><td>Report Group</td><td>ReportGroup</td><td>Domain</td></tr><tr><td>Apps</td><td>App</td><td>Report</td><td>Report</td><td>Presentation Layer</td></tr><tr><td>Apps</td><td>App Description</td><td>Source Description</td><td>Description</td><td>-</td></tr><tr><td>Sheet</td><td>Sheet</td><td>Report</td><td>Report</td><td>Sheet</td></tr><tr><td>Sheet</td><td>Sheet description</td><td>Source Description</td><td>Description</td><td>-</td></tr><tr><td>Cells</td><td>Cell</td><td>Report</td><td>Report</td><td>Cell Type</td></tr><tr><td>Cells</td><td>Cell Description</td><td>Source Description</td><td>Description</td><td>-</td></tr><tr><td>Measures</td><td>Measure</td><td>Report Field</td><td>Report Field</td><td>Measure</td></tr><tr><td>Measures</td><td>Measure Name</td><td>Name</td><td>Report Field</td><td>Measure</td></tr><tr><td>Measures</td><td>Measure formula</td><td>Formula</td><td>Report Field</td><td>Measure</td></tr><tr><td>Measures</td><td>Measure Description</td><td>Description</td><td>Report Field</td><td>Measure</td></tr><tr><td>Dimensions</td><td>Dimension</td><td>Report Field</td><td>Report Field</td><td>Dimension</td></tr><tr><td>Dimensions</td><td>Dimension Name</td><td>Name</td><td>Report Field</td><td>Dimension</td></tr><tr><td>Dimensions</td><td>Dimension Formula</td><td>Formula</td><td>Report Field</td><td>Dimension</td></tr><tr><td>Dimensions</td><td>Dimension description</td><td>Description</td><td>Report Field</td><td>Dimension</td></tr><tr><td>Master Objects</td><td>Master Object</td><td>Report Field</td><td>Report Field</td><td>Master Object</td></tr><tr><td>Master Objects</td><td>Master Object Name</td><td>Name</td><td>Report Field</td><td>Master Object</td></tr><tr><td>Master Objects</td><td>Master Object Formula</td><td>Formula</td><td>Report Field</td><td>Master Object</td></tr><tr><td>Master Objects</td><td>Master Object Description</td><td>Description</td><td>Report Field</td><td>Master Object</td></tr><tr><td>Variables</td><td>Variable</td><td>Report Field</td><td>Report Field</td><td>Variable</td></tr><tr><td>Variables</td><td>Variable Name</td><td>Name</td><td>Report Field</td><td>Variable</td></tr><tr><td>Variables</td><td>Variable Value</td><td>Formula</td><td>Report Field</td><td>Variable</td></tr><tr><td>Source Code</td><td>Script Info</td><td>Source Code</td><td>Source Code</td><td>Script</td></tr><tr><td>Source Code</td><td>Script Content</td><td>Code</td><td>Source Code</td><td>Script</td></tr><tr><td>Source Code</td><td>Script Name</td><td>Source Code Name</td><td>Source Code</td><td>Script</td></tr></tbody></table>

## Set up a Connection

### Prerequisites

The prerequisites to establish a connection:

### **Service Account User Permissions**

{% hint style="info" %}
It is recommended to use a dedicated service account to establish the connection to the data source, configured with the following minimum set of permissions.
{% endhint %}

{% hint style="info" %}
👨‍💻 Who can provide these permissions? The QlikView administrator grants these permissions, since users may not have sufficient access to assign them.
{% endhint %}

| Operations           | Access Permission                    |
| -------------------- | ------------------------------------ |
| Connector Validation | Access to the QVS and QVW files Path |
| Crawling             | Access to the QVS and QVW files Path |
| Lineage              | Access to the QVS and QVW files Path |
| Delta Crawl          | Access to the QVS and QVW files Path |
| Apps                 | Access to the QVS and QVW files Path |

### Connection Configuration Steps

{% hint style="info" %}
Users must have the Connector Creator role to configure a new connection.
{% endhint %}

1. Log into OvalEdge, go to Administration > Connectors, click + **(New Connector)**, search for **QlikView**, and enter the required parameters.\
   **Note**: Fields marked with an asterisk (\*) are mandatory for establishing a connection.

<table data-search="false"><thead><tr><th width="218">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "QlikView" is displayed as the selected connector type.</td></tr><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selection.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp</li><li>Azure Key Vault</li></ul><p>For more details, click <a href="https://docs.ovaledge.com/release8.1/connectors/additional-requirements/credential-manager-configuration">here</a>.</p></td></tr><tr><td>License Add-On</td><td><p><code>Auto Lineage - Supported</code><br><code>Data Quality - Not Supported</code></p><p><code>Data Access - Not Supported</code><br></p><ul><li>Select the Auto Lineage Add-On checkbox to build data lineage automatically.</li></ul><p>For more details, click <a href="https://docs.ovaledge.com/release8.1/connectors/introduction-to-connectors/setup-and-connectivity/license-types-and-add-ons?fallback=true">here</a>.</p></td></tr><tr><td>Auto Lineage</td><td>Supported</td></tr><tr><td>Data Quality</td><td>Not Supported</td></tr><tr><td>Data Access</td><td>Not Supported</td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the QlikView connection              </p><p>(Example: "QlikView_Prod").</p></td></tr><tr><td>Connector Description</td><td>Enter the description related to the connector.</td></tr><tr><td>Connector Environment</td><td>Select the environment (Example: PROD, STG) configured for the connector.<br><br>For more details, click <a href="https://docs.ovaledge.com/release8.1/connectors/introduction-to-connectors/setup-and-connectivity/prerequisites#connector-environment">here</a>.</td></tr><tr><td>Source Documents Path*</td><td>Enter the path to the source document file where the QVS and QVW files are located.</td></tr><tr><td>Logs Path</td><td>Enter the path to the QlikView logs folder.</td></tr></tbody></table>

**Default Governance Roles**

<table data-header-hidden><thead><tr><th width="218"></th><th></th></tr></thead><tbody><tr><td>Default Governance Roles*</td><td>Select the appropriate users or teams for each governance role from the drop-down list. All users and teams configured in OvalEdge Security are displayed for selection.</td></tr></tbody></table>

**Admin Roles**

<table data-header-hidden><thead><tr><th width="218"></th><th></th></tr></thead><tbody><tr><td>Admin Roles*</td><td>Select one or more users from the dropdown list for Integration Admin and Security &#x26; Governance Admin. All users configured in OvalEdge Security are available for selection.</td></tr></tbody></table>

**No of Archive Objects**

<table data-header-hidden><thead><tr><th width="218"></th><th></th></tr></thead><tbody><tr><td>No Of Archive Objects*</td><td><p>This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.</p><p>Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.</p></td></tr></tbody></table>

**Bridge**

<table data-header-hidden><thead><tr><th width="218"></th><th></th></tr></thead><tbody><tr><td>Select Bridge*</td><td><p>If applicable, select the bridge from the drop-down list.</p><p>The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.</p></td></tr></tbody></table>

2. After entering all connection details, the following actions can be performed:
   1. Click **Validate** to verify the connection.
   2. Click **Save** to store the connection for future use.
   3. Click **Save & Configure** to apply additional settings before saving.
3. The saved connection will appear on the Connectors home page.

## Manage Connector Operations

### Crawl/Profile

{% hint style="info" %}
To perform crawl operations, users must be assigned the Integration Admin role.
{% endhint %}

The **Crawl/Profile** button allows users to select one or more schemas for crawling and profiling.

1. Navigate to the **Connectors page** and click **Crawl/Profile**.
2. Select the schemas to be crawled.
3. The **Crawl** option is selected by default. To perform both operations, select the **Crawl & Profile** radio button.
4. Click **Run** to collect metadata from the connected source and load it into the Data Catalog.
5. After a successful crawl, the information appears in the **Data Catalog > Report / Report Column** tab.

The **Schedule** checkbox allows automated crawling and profiling at defined intervals, from a minute to a year.

1. Click the **Schedule** checkbox to enable the **Select Period** drop-down.
2. Select a time period for the operation from the drop-down menu.
3. Click **Schedule** to initiate metadata collection from the connected source.
4. The system will automatically execute the selected operation (**Crawl** or **Crawl & Profile**) at the scheduled time.

### Other Operations

The **Connectors page** provides a centralized view of all configured connectors and their health status.

**Managing connectors includes**:

* **Connectors Health**: Displays the current status of each connector, with a **green** icon for active connections and a **red** icon for inactive connections, helping monitor connectivity to data sources.
* **Viewing**: Click the **Eye** icon next to the connector name to view connector details, including Reports, Report Columns, and Report Group.

**Nine Dots Menu Options**:

To view, edit, validate, build lineage, configure, or delete connectors, click on the Nine Dots menu.

* **Edit Connector**: Update and revalidate the data source.
* **Validate Connector**: Check the integrity of the connection.
* **Settings**: Modify connector settings.
  * **Crawler**: Configure data extraction.
  * **Access Instructions**: Add notes on how data can be accessed.
  * **Business Glossary Settings**: Manage term associations at the connector level.
  * **Lineage**: Select server dialects for parsing and setting connector priority for table lineage.
  * **Others**: Configure notification recipients for metadata changes.
* **Build Lineage**: Automatically build data lineage using source code parsing.
* **Delete Connector**: Remove a connector with confirmation.

For more details on connector settings, click [here](https://docs.ovaledge.com/release8.1/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings).

***

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/release8.2/connectors/connector-repositories/reporting-tool/qlikview.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.