Datasources - Qlik Sense SaaS App

Created date: 17.7.2024

Updated by: Emma Camacho

Create: Qlik Sense SaaS App Datasource

Connect to a Qlik Sense App running in Qlik Sense SaaS.

GENERAL

The NAME is the M&D internal name for this App. It doesnt have to match the name in Qlik Sense, but it is recommended to have the same or a similar name.

The URL should be the URL of the Qlik Cloud. For example, https://company.eu.qlikcloud.com/. 

Naming convention. Depending on your Datasources, Reports and Tasks, it is convienient to define a naming convention. 

For example,
DATASOURCES
01.01 QS OnP Finance App
01.02 QS OnP Logistics App
02.01 QS SaaS Operations App
03.01 SF db Tracking App
REPORTS
01.01 001 Report 1 about Finance App
01.01 002 Report 2 about Finance App
TASKS
01.01 001 T000 Task creating and distributing Report 1

AUTHENTICATION TYPE defines how to connect to Qlik Sense SaaS.

The default is to use the API Key. 

Attention: It is recommended to create a User in Qlik Sense SaaS that has access only to the Apps that will be used in M&D and create the API Key using this User.

To ease the administration, it is recommended to change the setting in Qlik Sense Console, to allow a token to live longer.

Example, Change maximum token expiration: 10000 will allow the API Key to live 27 years.

Use AUTHENTICATION TYPE: API Key when the App doesnt have section access, or if it has section access it will be used only to burst reports via email, sharepoint, etc. If the App has section access, the service account should be ADMIN in the access list.

Use AUTHENTICATION TYPE: Impersonation (Section Access) if this datasource will be used together with the M&D Report Requester and/or Visualization Exporter Extensions for Qlik Sense AND the App has section access.

More information: Datasource - Qlik Sense SaaS App - Impersonation (Section Access)

Press the sync icon to get the list of Apps that are available. If the list of Apps is too long, it is convenient to reduce this list by adding a Qlik Sense Stream Filter in the Workspace properties.

More information: Best Practices: Workspaces

ADDITIONAL SETTINGS

Attention: If the App is very big and/or has many sheets and objects, it is highly recommended to use the Set Filter Before Rebuilding Cache option together with a Filter Field Name and Filter Value to reduce the time when rebuilding the cache.

What is the Cache?

It is a dictonary of all the fields, variables and id of objects in the App. It is only metadata.

What does it mean Rebuild the Cache?

It is the process of creating this dictonary of metadata.

When is it necessary to Rebuild the Cache?

When new objects, fields or variables were added to the App and M&D needs these new elements in a report and/or task.

Why Rebuilding the Cache can take very long?

M&D will request Qlik Sense to open the App and it will visit every sheet gathering all the object id's present in the sheet. Qlik Sense will load the App into memory and it will do all the necessary calculations to render all the charts and tables present in the sheet, and for every sheet. If it is a very big app with many sheets and objects, the process can take long.

How to minimize the time to Rebuild the Cache?

Use the option Set Filter Before Rebuilding Cache together with a Filter Field Name and Filter Value to set a filter that will load as few rows as possible, making the process of creating the dictionary/rebuilding the cache much faster. 

When setting the option Set Filter Before Rebuilding Cache, is the dataset reduced when distribuiting Reports?

No, the dataset is only reduced when rebuilding the cache/creating the dictionary. It is not reduced when distribuiting reports.

How to Rebuild the Cache?

Press the sync icon on the list of Datasources.

More information:  Using Qlik Sense Themes

The option Preload App is deprecated, no need to use it.

The Has Dynamic culture option should be used if the App is prepared to support different regional settings and the Decimal and Thousand separator are stored in a field.