Qlik operating model (in preview)

Overview and diagram view

Synchronizing means refreshing the assets that are currently in Data Catalog as a result of a previous ingestion or synchronization job. After synchronizing Qlik, the assets in Data Catalog accurately reflect the metadata as it exists at the time of synchronization.

Note 

The following image shows the relations between Qlik asset types.

You can easily recreate this diagram view in your Collibra environment. See Create a Qlik operating model diagram view.

Harvested metadata per asset type

This table shows the harvested Qlik metadata for each Qlik asset type.

Asset type

Synchronized metadata

Public ID

Qlik Server

Public ID: QlikServer

Description

Description
URL Url
Server (Qlik Server) hosts / is hosted in Business Dimension (Qlik Space) ServerHostsBusinessDimension

Qlik Space

Public ID: QlikSpace

Description Description
Description from source system DescriptionFromSourceSystem
Document creation date DocumentCreationDate
Document modification date DocumentModificationDate

Owner in Source

The only harvested metadata are email addresses.

OwnerInSource
Business Dimension (Qlik Space) groups / is grouped into Report (Qlik Sense Application) BusinessDimensionGroupsReport

Qlik Sense Application

Public ID: QlikSenseApplication

Description

Description
Description from source system DescriptionFromSourceSystem
Document creation date DocumentCreationDate
Document modification date DocumentModificationDate

Owner in Source

The only harvested metadata are email addresses.

OwnerInSource
State State
Report (Qlik Sense Application) groups / is grouped into Report (Qlik Story or Qlik Sheet) ReportGroupsReport
BI Report (Qlik Sense Application) contains / contained in BI Data Model (Qlik Data Model) BIReportContainsBIDataModel

Qlik Sheet

Public ID: QlikSheet

Description

Description
Description from source system DescriptionFromSourceSystem
Report (Qlik Sheet) uses / used in Report Attribute (Qlik Visualization) ReportUsesReportAttribute

Qlik Story

Public ID: QlikStory

Description Description
Description from source system DescriptionFromSourceSystem
Document creation date DocumentCreationDate
Report (Qlik Story) uses / used in Report (Qlik Sheet) ReportUsesReport

Qlik Visualization

Public ID: QlikVisualization

Description Description
Description from source system DescriptionFromSourceSystem

Report (Qlik Visualization) uses / used in Data Attribute (Qlik Data Attribute)

ReportUsesDataAttribute

Qlik Data Model

Public ID: QlikDataModel

No attributes. This is only a connecting point for related assets.

Data Entity (Qlik Data Entity) is part of / contains Data Model (Qlik Data Model)

DataEntityIsPartOfDataModel

Qlik Data Entity

Public ID: QlikDataEntity

Description Description
Location Location
Table Type TableType
Data Entity (Qlik Data Entity) contains / is part of Data Attribute (Qlik Data Attribute) DataEntityContainsDataAttribute

Qlik Data Attribute

Public ID: QlikDataAttribute

Column Position ColumnPosition
Definition Definition
Description Description
Technical Data Type TechnicalDataType
Data Element (Qlik Data Attribute) targets / sources Data Element (Column) DataElementTargetsDataElement

Example of ingested Qlik metadata

The following image shows an example structure after synchronizing Qlik.

Recommended hierarchy within a domain

You can enable hierarchies for the domain (or domains) in which your Qlik assets were ingested. Doing so makes it easier to understand the relation between your Qlik assets when viewing the assets on the domain page.

Follow these steps to enable and configure the recommended hierarchy.

Steps

  1. Open the domain page of the relevant BI Catalog domain.
  2. On the content toolbar, click .
    The Configure Hierarchy dialog box appears.
  3. Select Enable Hierarchy.
  4. Select Multipath.
  5. Start typing and select each of the following relation types:
    • Server hosts Business Dimension
    • Business Dimension groups Reports
    • Report is grouped into Report
    • Report used in Report
    • Report uses Report
    • BI Report contains BI Data Model
    • Data Model contains Data Entity
    • Data Entity contains Data Attribute
    • Data Element targets Data Element
  6. Click Apply.

Note 

Create a Qlik operating model diagram view

You can create a Qlik-specific diagram view, to visualize the operating model. The following procedure provides instruction on how to quickly create a new diagram view by copying and pasting the JSON code in the diagram view text editor.

Steps

  1. Open the asset page.
  2. Click the Diagram tab.
    The diagram is shown in the default diagram view.
  3. Click to add a new view.
  4. Select the Text option below the diagram view name.
    The diagram view text editor is shown.
  5. Copy the code from the Show JSON code section below and paste it in the diagram view text editor.
  6. Click Save.
  7. Edit the name and description of the diagram view as needed.