Skip to main content Skip to complementary content
Qlik Resources

Connecting Qlik NPrinting with QlikView

You must connect your Qlik NPrinting installation to QlikView if you want QlikView charts in your reports.

QlikView documents can be saved in local folders, on network shared folders, or on a QlikView Server.

Information noteThis page outlines how to connect to a QlikView server. To connect specific QlikView documents to Qlik NPrinting in order to create reports, see: Connecting to QlikView documents.

Requirements

QlikView Desktop

QlikView Desktop is required on the Qlik NPrinting Engine computer. QlikView Server and QlikView Desktop must be the exact same version, including the release number. QlikView Desktop must be installed locally on the same physical or virtual computer as the Qlik NPrinting Engine. QlikView Desktop is not required if you are only connecting to Qlik Sense apps.

For QlikView version compatibility, see QlikView compatibility. Note that your Qlik NPrinting version must be equal to or higher than your QlikView version.

QlikView Server

To generate reports using QlikView Server connections, the following are required:

  • Access to at least one QlikView Server.
  • The Windows user that runs the Qlik NPrinting Engine Windows service must belong to the QlikView Administrators Windows group on the QlikView Server computer.
  • To configure Qlik NPrinting for NTFS authorization, it must be configured in the Qlik Management Console. This means that the Windows operating system controls the file (document) access for users and groups through the NTFS security settings.
  • To configure Qlik NPrinting for DMS authorization QlikView controlled file access, see: JWT authentication.

QlikView Cluster

To generate reports using QlikView Cluster connections, the following are required:

  • Access to at least one QlikView Server.
  • The Windows user that runs the Qlik NPrinting Engine Windows service must belong to the QlikView Administrators Windows group on the QlikView Server computer.
  • To configure Qlik NPrinting for NTFS authorization, it must be configured in the Qlik Management Console. This means that the Windows operating system controls the file (document) access for users and groups through the NTFS security settings.
  • To configure Qlik NPrinting for DMS authorization QlikView controlled file access, see: JWT authentication.

To create a connection to a QlikView Cluster, the user that runs the Qlik NPrinting Engine service must:

  • Be a domain user.
  • Be part of QlikView Administrators security group in all the nodes of the cluster.
  • Be part of QlikView Management API security group in the computer where QMS runs.

Section access

If you are using section access, the following are required:

  • Connections must be configured to use server authentication.
  • A domain account must be configured in user settings, independent of the authentication type enabled in the Qlik NPrinting general settings.
Warning noteSection access is not fully supported for local QlikView documents. If you connect to a local QlikView document with section access, report recipients will see all available data, as if section access was not applied. You must use Qlik NPrinting filters or connect to documents via QlikView Server to ensure users only receive permitted data.

Licensing

To start the Qlik NPrinting service and connect to QlikView, you must have one of the following:

  • A named user Client Access License (CAL) that is manually assigned to the Qlik NPrinting Engine service user active directory account, on the QlikView Server.
  • A local QlikView Desktop license.

Users connecting through the API must be members of the QlikView Management API security group. The group is not created during the installation and must be added and populated manually, for example, with the members of the QlikView Administrators group.

Limitations

You cannot use the same user to run a QlikView service and Qlik NPrinting service.

Differences between QlikView server and local QlikView connections

There are benefits to connecting to a QlikView server:

  • Better performance
  • More stability
  • Section access
  • Increased security
  • Automatic data refreshes (no need to trigger a metadata reload)

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here