Qlik Extract


This extract type provides data extraction from QlikSense Server. You must first define a Qlik Virtual Proxy, as described in the article Qlik Connection.

Main Settings

Qlik Connection

Name of the Qlik Connection.

 Qlik Application Name*

Name of the Qlik application. Note that applications are hidden to the outside until they are published.

Qlik Table Name*

Name of one table of the data structure that Qlik Application uses. Tables can be seen from the  Data Manager on the Qlik server.

Row Count (optional)

The total number of rows that can be fetched from the server. Maximum number is 2.147.483.647 (default value).

Offset (optional)

Sets a unit to offset from the beginning of the table.


* If the connection is configured correctly, this drop-down menu will fetch menu items dynamically from the server.


  • If Qlik Sense server exists outside of the corporate firewall/network, then it might be necessary to add the IP or host name of the Qlik server to Qlik host whitelist, which enables Qlik engine communication. If this is not done, the Qlik extract test will fail, even if the Qlik connection test is successful.
  • In contrast to Qlik LOAD, which uses QMC API, Qlik Extract technically uses the Qlik engine API to provide data from the Qlik server based on WebSocket technology.
  • If UDC for LDAP is not configured properly in Qlik Management Console, users will encounter the following warning in the Qlik Management Console’s Edit User Directory screen. They will be able to connect to Qlik, but the extract won’t return any data. Jedox only supports Active User Directory. See Qlik Connection for more information.