Scripts need to be exported using the Qlik Sense Engine APIs.

Resolution

The Engine API and the Capability API both have a method/function called GetScript() that will allow the app script to be exported. Once the script is accessed, it can be saved to disc, for example, a folder that is perhaps monitored by a change control system. The Engine API can be found here and the Capability API can be found here. The following are examples of both APIs:

Engine API:

IAppIdentifier foundAppIdentifier = _location.AppWithId("....appId....");
IApp app = _location.App(foundAppIdentifier);
string script = app.GetScript();
Console.WriteLine(script);

Capability API:

var app = qlik.openApp("....appId....");
app.getScript().then( function(script){
  console.log(script);
});

Related Content:

Get started with APIs on Windows 
GetScript Method (Engine)
getScript method (Capability API)

Qlik Sense: call Qlik Sense Engine API with Python 
Qlik Sense Repository API/Engine API(Enigma.js) example with JWT authentication: duplicate/scramble/export 
Qlik Sense: Getting started with the .NET SDK 

How many days are On-Demand request coming from Qlik Sense or QlikView kept in memory? Where are they saved?

Is it possible to change this?

Environment:

• Qlik NPrinting 

The days NPrinting keeps an On-Demand request in memory depends on a parameter that can be added in the scheduler.config file.

Resolution:

The NPrinting On-Demand requests (both QlikView and Qlik Sense) are kept in memory in the "C:\ProgramData\NPrinting\ondemand\responses" folder for  some days and then automatically removed:

•  completed requests remain for 30 days
• aborted requests and failed requests are kept in memory for 6 days

It is possible to change these values by adding an entry in the "scheduler.config" file that is saved in "C:\Program Files\NPrintingServer\NPrinting\Scheduler":

1.  To change the days to keep for completed requests, add this tag and specify the number of days:         
   

   <add key="completed-days-to-keep" value="30" />​

2. To change the days to keep for aborted requests, add this tag and specify the number of days:
   

    <add key="aborted-days-to-keep" value="6" />​

!Note: NPrinting Installations, system folders and files are limited to the "c drive"  where the installation is performed by default. This point remains documented in each Qlik NPrinting Product Release notes.

For details visit: Qlik NPrinting Known issues and limitations. File and folder redirection to different local or network locations is not currently available.

Or: How to move Qlik Sense database to a standalone PostgreSQL server?

The Qlik Sense Repository Database (QSR) can be moved to a dedicated standalone PostgreSQL instance not hosted on the same machine as other Qlik Sense Services. It is also possible to move an already existing QSR from a local Sense install, to a dedicated PostgresSQL database.

Environment

• Qlik Sense Enterprise on Windows , September 2017 and up

Set up a postgresSQL database

Instructions for this might vary slightly. Please refer to the Qlik Online Help for details.  We recommend watching this video.

Qlik Sense Enterprise server has a set of five databases. For more details visit Installing and configuring PostgreSQL on help.qlik.com.

1. The Qlik Sense repository database (QSR):

The QSR is the primary database in your Qlik Sense deployment.

2. The Qlik Sense services database (SenseServices):

The SenseServices database contains schemas for each of the Qlik Sense services and allows growth independently of the Qlik Sense Repository Database, while still sharing the same PostgreSQL instance and login role.

3. The Qlik Sense message queue database (QSMQ):

The QSMQ database provides a light-weight method of passing messages internally between services in Qlik Sense Enterprise. The NOTIFY and LISTEN functionality in PostgreSQL allows services to be notified about new messages that have been written to the messaging table.

4. The Qlik Sense logging database (QLogs):

The QLogs database centralizes logging by collecting log messages from all Qlik Sense nodes in your deployment and stores them in a PostgreSQL database.

5. The Qlik Sense license service database (Licenses):

The Licenses database is used to sync the assignments between the Qlik license backend and the local installation.

Simplified checklist of steps:

1. Download a valid version of postgresSQL.  For Sense June 2017 and up, 9.6.x is required, from November 2019 version 11.5.x as well. From May 2021 version 12.5 can be used. Review the system requirements of your version before proceeding.
2. Install based on instructions found on the Qlik Online Help for Qlik Sense; select the version you are running on then select from Menu , Deploy - Qlik Sense installation - Installing and configuring PostgreSQL.

Moving the Qlik Sense Share Folders as well?

Follow How to change the shared path in Qlik Sense 

Backup 

Depending on the version, you need to backup different databases, on the current Qlik Sense central node hosting the Qlik Sense Repository Database service, follow the backup instructions to obtain a database copy of each Qlik Sense Database Present . 
   Example for February 2021  you need to backup the databases reported in section "Installing and configuring PostgreSQL"; referring to the Help site these are : 
    QSR , QSMQ , SenseServices , Licenses , if configured QLogs    

Restore

On the dedicated remote postgresSQL host, perform a restore   of the backed up Databases of previous point. 

Changing the Connection String to QSR and QSMQ Database 

1. On the Qlik Sense central node, all services but the Qlik Sense Repository Service are shut down.
2. Open QlikSenseUtil. By default, this will be installed in: C:\Program Files\Qlik\Sense\Repository\Util\QlikSenseUtil\QlikSenseUtil.exe
3. Open the Connection String Editor and Read the current configuration, decrypting the current data.
   
   
4. Replace all mentions of the current database hostname.  In our example, the new database resides on 172.16.16.103. Instead of an IP you can also use the FQDN of the db server.
5. You need to repeat this step for the   sections <add name="QSMQ" and <add name="postgres"
6. Hit Save Value in config file encrypted, committing any changes. 

Changing the Connection String to SenseServices Databases. 

       Execute steps in Moved Postgress database to new host, but some qliksense is still accessing the SenseServices old database; check if different version of article are present for different Qlik Sense version .

Changing the Connection String to Licenses Database ( April 2019 and up ) 

Starting from April 2019 new License Service implementation is using this database.

1.   Open an elevated Powershell and change directory to C:\Program Files\Qlik\Sense\Licenses
2.    Run the script .\Configure-Service.ps1 and provide:
   • new Hostname or IP  
   • database port default is 4432
   • database user qliksenserepository
   • databasepassword is the qliksenserepository password  used during configuration of  the new database.
3. example: 
4. cd  'C:\Program Files\Qlik\Sense\Licenses'
5. .\Configure-Service.ps1 172.16.16.102 4432 qliksenserepository Password123!

It will look like this:

repeat this for:

Update the Qlik Logging Service Connection String     

If the QLogs needs to be update you could check on help.qlik.com the section "Updating the connection string parameters" providing new hostname or ip. 

Remove Database Service dependency and Postgres Server ( to avoid issues with future Upgrade of Environment)

Qlik Sense Repository service dependency on the Database service needs to be removed and Database needs to be removed. 

In an elevated command prompt, execute the following on prompt:

c:\sc config "QlikSenseRepositoryService" depend= ""
c:\sc config "QlikLoggingService" depend= ""

This should return: 

[SC] ChangeServiceConfig SUCCESS

Restart the Qlik Sense Repository Service.

Check that Qlik Sense Repository Database doesn't start (confirms [SC] ChangeServiceConfig SUCCESS ).

Remove the (local) Qlik Sense Repository Database

Find the most recent PostgreSQL.msi in C:\ProgramData\Package Cache\  and remove it. This removes the service but no old local database data. This is needed to prevent issues on future upgrades of Environment.
You can find the precise folder with this command depending on the Postgresql Version you used installing the inital release.

9.6:

c:\cd ProgramData\Package Cache
c:\ProgramData\Package Cache\dir /s PostgreSQL.msi
The folder containing PostgreSQL.msi will be revealed.
Right click on the PostgreSQL.msi file and select uninstall from the menu.

12.5:

c:\cd ProgramData\Package Cache
c:\ProgramData\Package Cache\dir /s PostgreSQL125.msi
The folder containing PostgreSQL.msi will be revealed.
Right click on the PostgreSQL.msi file and select uninstall from the menu.

Finalize

1. Restart the Qlik Sense Repository Service and verify that Qlik Sense Repository Database Service doesn't exist when followed the previous steps.
2. Start all remaining Sense Services 
3. Progress on the startup sequence (including the connection to the new database) can be tracked in the _System_Repository log files located in C:\ProgramData\Qlik\Sense\Log\Repository\Trace
4. Verify functionality.

5. In Multi-node scenario you need to repeat steps "Changing the Connection Strings to Databases" on all Rim nodes (QlikSenseUtil for Repository.exe.config and Configure-Service.ps1 for the micro services), and if required configure "Update the Qlik Logging Service Connection String" (note that is EOL with Qlik Sense Enterprise on Windows February 2022) .   

6. This article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

This Support article covers functionality available in the new Qlik PostgreSQL Installer (QPI), which allows you to upgrade an existing Qlik Sense Repository Database (QRD) from PostgreSQL 9.6 to PostgreSQL 12.5, or install a brand new QRD based on PostgreSQL 12.5.

PostgreSQL 9.6 has reached End of Life Reference: PostgreSQL Versioning Policy 

>> Qlik PostgreSQL Installer - Download Link <<

Environment

• New Qlik Sense Repository Database (QRD) setups for, compatible with Qlik Sense Enterprise Client Managed since November 2019 - Reference: Qlik Sense's compatibility with PostgreSQL for the... - Qlik Community - 1716510
• Existing QRD setups running Qlik Sense embedded PostgreSQL 9.6 (Qlik Sense February 2022 and higher)

Supported Scenarios

• Upgrading an existing QRD from PostgreSQL 9.6 to 12.5. Upgrading earlier versions of QRD is not supported via this method. Instead, upgrade to a version of Qlik Sense that supports 9.6 to automatically migrate through this minor version - List of supported PostgreSQL and early Qlik Sense versions
• Installing a new QRD cluster on a new server, for a new environment or to migrate an existing Database to a separate host.
• Qlik Sense Enterprise on Windows February 2022 and above are supported versions for QPI. Upgrade to a supported version for QPI first and then use QPI to upgrade PostgreSQL.

Considerations

• This installer will not detect a standalone PostgreSQL database installed by any other means, other than through an official Qlik installer package
• The installer itself does not provide a rollback feature, this is described below
• The user who runs the installer has sufficient permissions to execute it and install services
• The user who runs the installer has sufficient permissions to create folders and files in the backup destination
• The backup destination has sufficient free disk space to dump the existing database 
• The backup destination is not a network path or virtual storage folder. It is recommended the backup is stored on the main drive
• There will be downtime during this operation, please plan accordingly

Installing a new Qlik Sense Repository Database using PostgreSQL 12.5

1. All services on rim nodes must be stopped
2. Run the Qlik PostgreSQL Installer 
3. Click on "Install"
4. Accept the Qlik Customer Agreement
5. Set your "Local database settings" and click "Next". You will use these details to connect other nodes to the same cluster
6. Set your "Database superuser password" and click "Next"
7. Review your settings and click "Install", then click "Finish"
8. Restore your existing QRD backup OR
9. Start installing Qlik Sense Enterprise Client Managed, connecting to an existing cluster 

A new service will now be present in your Services management console: 

If you are migrating your existing databases to a new host, please remember to reconfigure your nodes to connect to the correct host. How to configure Qlik Sense to use a dedicated Pos... - Qlik Community - 1791775

The tool will display information on the actions being performed. Once installation is finished, you can close the installer. 

The PostgreSQL package can be removed via the Control Panel in case you need to uninstall the database at one point. 

Upgrading an existing QRD to PostgreSQL 12.5 - Central Node

It is recommended that you first upgrade Qlik Sense to a version that supports QPI, starting with the February 2022 release. More information on Qlik Sense and PostgreSQL compatibility.

Installations other than in C:\Program Files\Qlik\Sense are not supported at the moment.

In this scenario, the new QRD will be using the same port as the old service, and rim nodes do not need any further reconfiguration. 

1. Stop all services on rim nodes
2. On your Central Node, stop all services but Qlik Sense Repository Database
3. Run the Qlik PostgreSQL Installer, an existing Database will be detected
4. Click on "Upgrade"
5. Accept the Qlik Customer Agreement
6. Provide your existing "Database superuser password" and click "Next"
7. Set your desired backup location and click "Next"
8. Click "Upgrade", then exit by clicking "Finish"
9. Start all other services on Central Node
10. Start all services on all other nodes

Final steps

At this point, it is important to validate that all services and nodes are operating as expected. If it seems like some data is missing from the QMC or elsewhere, you may revert back to the old database instance. To do this, stop the newly installed "postgresql-x64-12" service and set its startup type to Manual. Then start the original "Qlik Sense Repository Database" service, along with all other services. 

Once the upgrade and all validation is complete, the old Qlik Sense Repository Database service should be removed on the server. 

Perform the following steps to delete the Qlik Sense Repository Database Service

c:\cd ProgramData\Package Cache
c:\ProgramData\Package Cache\dir /s PostgreSQL.msi
The folder containing PostgreSQL.msi will be revealed.
Right click on the PostgreSQL.msi file and select uninstall from the menu.

This version is fully compatible with the official PostgreSQL installers from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads 

If you need to upgrade to a higher release than Qlik provides you can install the same major PostgreSQL release 12.x or up to version 13.

Troubleshooting

If the installation crashes, server reboots unexpectedly during this process or there is a power outage, the new database may not be in a serviceable state. Installation / upgrade logs are available in your temporary files location, for example: 

C:\Users\Username\AppData\Local\Temp\2

A backup of the original database contents is available in your chosen location, or by default in:

C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\backup\9.6

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support. The video in this article was recorded in a earlier version of QPI, some screens might differ a little bit.

>> Qlik PostgreSQL Installer - Download Link <<

Related Content

Techspert Talks - Upgrading Qlik Sense Repository Service
Backup and Restore Qlik Sense Enterprise documentation
Migrating Like a Boss
Optimizing Performance for Qlik Sense Enterprise
Qlik Sense Enterprise on Windows: How To Upgrade Standalone PostgreSQL
How-to reset forgotten PostgreSQL password in Qlik Sense
How to configure Qlik Sense to use a dedicated PostgreSQL database
Troubleshooting Qlik Sense Upgrades

 Click here for video transcript

After upgrading to Qlik Sense Enterprise November 2021 or a later version, users accessing with SAML authentication may experience issues accessing Qlik Sense, lose their rights and permissions, or experience other unusual behavior.

However, performing a UDC sync and connecting with Windows Authentication works without issue.

Environment

Qlik Sense Enterprise on Windows November 2021 and later releases

Cause

Prior to the November 2021 version of Qlik Sense, the attributes from SAML authentication were not persisted in Qlik Sense and were only used and seen in the logs during session setup.

Starting with November 2021 a product enhancement was made to persist. This was done so that custom rules could be written to more easily take advantage of the SAML attributes.

The problem arises from the fact that many existing SAML virtual proxies map SAML attributes to existing attributes used by the UDC, such as the Group attribute.

This means that when a user accesses Qlik Sense using SAML the Group attribute from the UDC will be overwritten with the SAML attribute. So if these two attributes are not identical any custom security rules written based on the attributes from UDC will no longer apply to the user trying to access Qlik Sense.

Resolution

There are several resolutions possible, but it is up to each customer to decide which is the best fit for them, primarily based on how much they are concerned with utilizing the attributes delivered by SAML.

1. Remove The Attribute Mapping From The Virtual Proxy

By simply removing the attribute mapping(s) from the virtual proxy settings you prevent Qlik Sense from overwriting the existing values pulled in by the UDC by not pulling in any values from the UDC.

2. Revert The Behavior And Disable Persistence

This is done by setting following flag to false in C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json, followed by restart of services.

{"contentHash":"2ae4a99c9f17ab76e1eeb27bc4211874","originalClassName":"FeatureToggle","flag":"SessionDataPersistanceEnabled","enabled":false}

3. Modify Existing Custom Rules To Accept Both Formats

This option is fairly straightforward in concept, without modifying the virtual proxy or any configs this allows both formats to work if there is a discrepancy between what the UDC and SAML are providing.

For most organizations, this is the most convoluted and labor-intensive solution on this list, but it is a valid option and included in the interest of providing all the options possible.

4. Change The Naming Of The Attribute Mapping In The Virtual Proxy Settings

Instead of mapping to Group (to continue using the scenario from above), you can change the attribute name the values are mapped to, such as GroupSAML for example.

Since this now maps to a different attribute it will not overwrite the values brought in by UDC. This allows existing rules to work and can be used if you'd like to shift your custom rules to utilizing SAML attributes while maintaining a UDC synch to pull in users

Options 1 & 2 prevent SAML from persisting data and are perfectly fine if you do not plan to use the SAML attributes to determine access and rights.

However, if you want to utilize the SAML attributes in your custom rules and use them to dictate access and rights then options 3 & 4 are viable.

Qlik Replicate connecting to DB2 z/OS fails with a Communication Link failure function detecting the error:

"selectForRecvTimeout". Protocol specific error code(s): "115", "*", "*". SQLSTATE=08001 SQL30081N. 

Environment

• Qlik Replicate all versions

Resolution

This error is an indication there is a connection issue from the Qlik Replicate Server to the z/OS environment as a general error. When a Task starts it can start up to six (6) threads connecting to the Source R4Z environment which are connections to the DDF DB2 environment. 

On z/OS run the below system command:

-DIS DDF Detail and check the output below as these are the Max Connections and Active Connections

DSNL090I DT=A CONDBAT= 400 MDBAT= 200
DSNL092I ADBAT= 45 QUEDBAT= 203 INADBAT= 0 CONQUED= 0

CONDBAT and MDBAT: These refer to two parameters, CONDBAT and MAXDBAT, in the Db2 subsystem's ZPARM module (think of the ZPARMs as Db2 for z/OS configuration parameters). CONDBAT specifies the maximum number of connections that DDF-using applications can have with the Db2 subsystem. MAXDBAT is the maximum number of those connections that can be active at one time

Cause 

CONDBAT and MDBAT: These refer to two parameters, CONDBAT and MAXDBAT, in the Db2 subsystem's ZPARM module (think of the ZPARMs as Db2 for z/OS configuration parameters) where set to low for the concurrent Qlik Replicate Tasks running against this Db2 environment.

Related Content

https://www.ibm.com/docs/en/db2-for-zos/11?topic=commands-display-ddf-db2

***Changes must be made to all Qlik servers that will not be provided with internet access.***

This is mainly due to the Qlik DataMarket reaching out to the internet although it may not even be used. Undoing or not agreeing to the Qlik DataMarket Terms of Service does not fully disable certain Qlik DataMarket functionalities.

NOTE: Qlik DataMarket has been discontinued. Qlik Sense Enterprise on Windows versions February 2021 and newer no longer included it. For  updated information see Qlik DataMarket will be retired  

For servers not connected to the internet, they may be prompted with a pop-up error when browsing in the Hub or in the Data Load Editor with the following errors:

• The Hub has continuous bubbles while loading forever
• The Hub is stock on the initial loading bar
• Failed To Load Connection - Qlik Sense 3.0.x - Feb2018
• Failed To Load Connection - Qlik Sense 2.2
• An Unknown Error Occurred - Qlik Sense 2.1.1 and 2.0.x

Browser Debug tools may display the following error in the console:
 

Cause:

The Qlik Sense DataMarket connector executable is cryptography signed for authenticity verification, and the .NET Framework's verification procedure when launching an executable includes checking OCSP and Certificate Revocation List information, which means fetching it online if the system doesn't have a fresh cached copy locally.

Qlik DataMarket connector will try to connect Internet to initialize and verify even without using it.

By making the changes in 3.x and June 2017 newer, Qlik Sense will not wait for a response on the verification step, which is the cause of the Failed To Load Connection and related error messages. It will also fix monitoring app issues and problems where the Data Load Editor loads forever. Note: it is highly suggested that all Qlik servers have internet access, however this will help to avoid some issues caused by it.
 

Resolution:

Option 1 will persist through upgrades, whereas Option 2 would have to be reapplied after every Sense upgrade. 

Option 1:

<runtime>     
     <generatePublisherEvidence enabled="false"/>  
</runtime>

<runtime>
    <generatePublisherEvidence enabled="false"/> 
</runtime>

<runtime>
  <some other key="value"/>
  <generatePublisherEvidence enabled="false"/>
</runtime>

4. Save machine.config
5. Repeat on all nodes (if applicable)
6. Start services on all nodes

<runtime>     
     <generatePublisherEvidence enabled="false"/>  
</runtime>

<runtime>
    <generatePublisherEvidence enabled="false"/> 
</runtime>

<runtime>
  <some other key="value"/>
  <generatePublisherEvidence enabled="false"/>
</runtime>

• C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage\QvOdbcConnectorPackage.exe.config
• C:\Program Files\Common Files\Qlik\Custom Data\QvDataMarketConnector\QvDataMarketConnector.exe.config
• C:\Program Files\Common Files\Qlik\Custom Data\QvSalesforceConnector\QvSalesforceConnector.exe.config
• C:\Program Files\Common Files\Qlik\Custom Data\QvEssbaseConnector
• C:\Program Files\Common Files\Qlik\Custom Data\QvRestConnector
• C:\Program Files\Common Files\Qlik\Custom Data\QvWebStorageProviderConnectorPackage

Qlik Sense connector (from the ODBC connector package like for example Oracle, MS SQL, Hive, Redshift, etc...) fails randomly with the following error message which can be found in the script and the Qlik ODBC connector package log:

Error: Connector connect error: Error starting QvConnect process: Instance 'QvOdbcConnectorPackage#1' does not exist in the specified Category.

Environment

• Qlik ODBC Connector Package May 2021 or lower 
• Qlik Sense Enterprise on Windows May 2021 or lower 

Resolution

The issue is related to a software defect and has been solved in the Qlik Sense version August 2021.

Upgrade your Qlik Sense version to any version after Qlik Sense August 2021. The ODBC connector package will be automatically upgraded as well.

Workaround:

Besides doing an upgrade to Qlik Sense August 2021, there are the following workarounds available:

1. Check if the affected connector has a connector reading strategy "engine" if yes, then try to change it to "connector", like for example  " <add key="redshift-reading-strategy" value="connector" />" (this can be done in the config file " QvOdbcConnectorPackage.exe.config" under "C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage"
2. Try to add "<add key="QlikEngineLocation" value="C:\Program Files\Qlik\Sense\Engine\QvConnect64.exe" />" in the ODBC connector package config file

Fix Version:

Qlik Sense August 2021

Cause

Product Defect ID: QB-3803

In larger organizations, the number of groups a user is a member of may exceed the limit that Azure Active Directory will add to a token. 150 groups for a SAML token, and 200 for a JWT. 

Environment

• Qlik Cloud 

Solution

Qlik Cloud does not read the groups into the ID token returned by Azure, but instead will fetch the groups for the user from the MS Graph API (a maximum of 1000 groups is fetched).

The groups are fetched from the following endpoint and nested groups are not supported.

https://docs.microsoft.com/en-us/graph/api/user-list-memberof

However, please note that if sending only specific groups to Qlik Sense is needed (and not all groups assigned to the user in Azure), then you will have to use the IdP type "ADFS" to read attributes from the ID token and use roles in Azure instead of groups to pass only the wanted groups.

https://joonasw.net/view/using-groups-vs-using-app-roles-in-azure-ad-apps

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Related Content 

https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-fed-group-claims

https://joonasw.net/view/using-groups-vs-using-app-roles-in-azure-ad-apps

When accessing the Qlik Cloud tenant through VPN, all vpn users are unable to download Qlik Cloud chart images and data with errors:

• Something went wrong or
• something went wrong with

Environment

• Qlik Cloud 

Resolution

• Check with your cloud security provider and ask them to insert your Qlik Cloud tenant address into its access whitelist for your environment

Cause

• Cloud related security platform such as zscalar.net blocks download of Qlik chart images and data

Related Content

• https://help.zscaler.com/zia

Internal Investigation ID

• QB-14441

Is it possible to disable the non-secure RC4 cipher in QlikView?

Environment

• QlikView 12.70 (May 2022) SR1

Resolution

QlikView 12.70  SR1 introduces the possibility of disabling RC4.

This will require applying a change to the QlikView Management Service and QlikView WebServer’s config settings and the QlikView Server's settings.ini.

This will also require applying a change to every client that needs to use the Open In Server (QlikView Desktop) functionality and for every client that uses the IE-Plugin on Microsoft Edge (Internet Explorer is no longer supported). 

Note: Clients using only AJAX (browser) or only opening local files (QlikView Desktop) will not require a setting change.

LIMITATION: disabling RC4 is currently not supported if QlikView Desktop or the IE-Plugin are running on Windows 2022.

Server-Side changes:

1. On all nodes, stop the QlikView WebServer (or Setting Service) and QlikView Management Service
2. Take a backup copy of the QVManagementService.exe.config (under C:\Program Files\QlikView\Management Service) and the QVWebServer.exe.config (under C:\Program Files\QlikView\Server\Web Server) config files
3. Using a text editor with administrator permissions, edit the two above-mentioned config files
4. Change ”true” in the line <add key="EnableRC4" value="true" /> --> to ”false”
5. Save the files and close
6. Restart the services

Further server-side changes (only needed for "Open in Server" and "IE-plugin"):

1. On all nodes, stop the QlikView Server (QVS.exe) service
2. Find the servers’ settings.ini files and take a backup copy
3. Edit the files
4. Change the line SessionAlgorithm=Legacy to SessionAlgorithm=CALG_AES_128
5. Save the files and close
6. Restart the QVS.exe service

Client-side changes:

(to be applied to each client using the IE-Plugin or the QlikView Desktop client's "Open in Server" functionality)

1. For each client, find the settings.ini file and take a backup copy
2. Edit the file
3. Change the line SessionAlgorithm=Legacy to SessionAlgorithm=CALG_AES_128
4. Save the file and close
5. Relaunch the client or browser

IMPORTANT: when using the IE-plugin or "Open In Server" the server and the clients will need to run on the same SessionAlgorithm, either Legacy (RC4 enabled) or CALG_AES_128 (RC4 disabled). Using different algorithms will break the connectivity between a client and a server. AJAX is not affected by this and does not require client-side changes. Changes are also not required if a Desktop client is only used to open local files (no connection to QVS).

The following error or similar could be generated when loading data of type NCLOB or CLOB from an Oracle Data Source.

ERROR [HY000] [Qlik][OracleOCI] (3000) Oracle Caller Interface: ORA-00942:the table or view does not exist

The issue was found after upgrading from a previous Qlik Sense version (example QS February 2021 SR4; QS May 2021 SR2) to QS May 2022 SR1 and SR2

Environment

• Qlik Sense Enterprise May 2022

Resolution

- Defect QB-10789 was reported to R&D

- We noticed that only  fields of data type NCLOB or CLOB are affected

- A patch with the fix is planned to be delivered with the Qlik Sense August 2022 Patch 1 version

Information provided on this defect is given as is at the time of documenting. For up to date information, please review the most recent Release Notes, or contact support with the ID QB-10789 for reference.

Workaround:

A workaround could be a downgrade of Qlik ODBC connector package to the previous working version. Alternatively you can reach out to Qlik Support in order to get a temporary fixed ODBC connector package version 6.191 (a new official patch will be provided soon).

Cause

Product Defect ID: QB-10789

Environment

• Replicate
• Table/Field level transformation

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Field Transformation

CLOB data types have a limitation in that no string functions can be performed on them in a field transformation. There will be no errors in the log file, just that the field will be NULL.

On my Source  table from SQL, I am using the source lookup function under Data Enrichment in order to retrieve the CLOB field value and then apply a string function (replaceChars) to it. 

By using the source lookup function on the filed it is returned to the replicate task in a form where a string function can be applied.

This source lookup function is documented in the replicate user guide and the on-line help.

The general form of the function is as follows:

source_lookup(TTL,'SCHM','TBL','EXP','COND',COND_PARAMS)

For this example I am doing the lookup into the MyClob table:

source_lookup(1,'DBO','MyClob','MyClob','MyID=?',$MyID)

I will then wrap this lookup in a replacechars function:

ReplaceChars(source_lookup(1,'DBO','MyClob','MyClob','MyID=?',$MyID),'L','@')

NO_CACHING is important to ensure it keeps changing for each value and doesn’t re-use values
DBOis the schema in oracle
MyCLOB is the table
MyClob is the field that I want returned
MyID=? is the predicate for the lookup 
$MyID is the value from the field that we are using in the predicate in place of =?

NOTE: That the lookup may have a performance implication and will need to be tested to see if it meets all of your latency criteria. 

I will show a series of screen shots below that demonstrate the results of this exercise for the target table:

Source DDL and data for MyClob table:

Target data for MyClob table (NO Transformations):

Target data for MyClob table (ReplaceChars() function on MyString and MyClob fields):

NOTE: There are no errors in the task log - just null values in the field.

MyString field transformation: replaceChars($MyClob,'M','@')

MyCLOB field transformation: replaceChars($MyClob,'L','@')

Target data for MyClob table (ReplaceChars(SourceLookup) function on MyClob fields):

NOTE: You will see that the replaceChars function worked.

MyString field transformation: replaceChars($MyClob,'M','@')

MyCLOB field transformation: ReplaceChars(source_lookup(1,'DBO','MyClob','MyClob','MyID=?',$MyID),'L','@')

Please feel free to try other string functions on the Clob field after once the source lookup returns the value. They should all work.

In this article, we will be walking through the basic troubleshooting steps required to look into Hadoop endpoint connectivity issues. 

These steps will focus on investigating two connections:

• HDFS connectivity
• HIVE connectivity

The Scenario

We have implemented two issues by blocking port 50070 and adding the wrong ODBC parameter for the Hive. The outlined troubleshooting steps will highlight how to identify these issues. 

In Replicate UI Go to Server Tab --> Logging --> Server Logging Levels and keep the COMMUNICATION and SERVER logging component to Trace during the troubleshooting.

As we begin, we can already see that the connection test fails when we click Test Connection. It fails with SYS-E-HTTPFAIL, Failed to connect to HDFS...

To view the Server logs go to Replicate UI --> Server Tab --> Logging --> Server Logging Levels --> View Logs --> Open the server log to see the below connectivity failed messages:

00011144: 2022-09-25T00:43:40:393877 [COMMUNICATION   ]T:  requested URL <http://10.51.2.44:50070/webhdfs/v1/?user.name=admin&op=GETFILESTATUS>, action is GET  (at_curl_http_client.c:504)

00011144: 2022-09-25T00:43:40:393877 [COMMUNICATION   ]T:  Clearing (if there is) curl old custom request  (at_curl_http_client.c:950)

00011144: 2022-09-25T00:43:40:393877 [COMMUNICATION   ]T:  calling user pre submit callback  (at_curl_http_client.c:1960)

00011144: 2022-09-25T00:43:40:393877 [COMMUNICATION   ]T:  user pre submit callback returned with status 0  (at_curl_http_client.c:1964)

00011144: 2022-09-25T00:43:40:393877 [COMMUNICATION   ]T:  preparing response structure; body will be written as dynamic string  (at_curl_http_client.c:1428)

00011144: 2022-09-25T00:43:40:395850 [COMMUNICATION   ]T:  AT_CURL->at_curl_easy_perform: curl_action_status == CURLE_OK failed  (at_curl.c:883)

00011144: 2022-09-25T00:43:40:395850 [COMMUNICATION   ]T:  Failed to curl_easy_perform: curl status = 7, Couldn't connect to server (Failed to connect to 10.51.2.44 port 50070: Bad access)  [1000143]  (at_curl.c:883)

The error Couldn't connect to server in the logs and Failed to connect in the UI indicates a connectivity issue and we will begin investigating there. 

1. Ping test.

This is a quick and common way to verify Hive and HDFS connectivity. It verifies if we have network connectivity at all. 

In a command line, we execute:

ping 10.51.2.44

Where 10.51.2.44 is the IP address of the destination server. 

Result:  PASS

2. Telnet Test

Depending on whether or not we are using Hive or HDFS, the ports used are different. It verifies if the port specified is being listened on.

In a command line, we execute:

telnet 10.51.2.44 50070

Where 10.51.2.44 is the IP address of the destination server. 

Result: FAIL

This indicates that port 50070 may not be available (blocked by a firewall, etc).

3. CURL Test

This test is only required for HDFS. We might need to use different authentication mechanisms with CURL based on the deployed authentication mechanisms (like Username\password, Kerberos with key tab, and Kerberos with AD Etc.,).

We must use the exact URL found in the Qlik Replicate log file.

In a command line, we execute:

curl -i -v "HTTP://10.51.2.44:50070/webhdfs/v1/user/admin/USER?user.name=admin&op?GETFILESTATUS"

Where 10.51.2.44 is the IP address of the destination server. 

Result: FAIL

Since both the CURL and Telnet tests failed, we look into port 50070 and identify that it has been blocked by a firewall. We enable the port and further tests show Telnet and CURL succeeding.

We can also verify the port using PowerShell and the following command:

Test-NetConnection -ComputerNamer 10.51.2.44 -Port 50070

This is an example of a successful CURL test:

However, when we test the connection in the UI, the connection still fails.

This time it displays a different error:

Cannot enable SSL for the connection when connecting to a server that has not enabled...

To view the Server logs go to Replicate UI --> Server Tab --> Logging --> Server Logging Levels --> View Logs --> Open the server log to see the below connectivity failed messages:

00028952: 2022-09-25T01:02:09:511445 [COMMUNICATION   ]T:  requested url <http://10.51.2.44:5 0070/webhdfs/v1/?user.name=admin&op=GETFILESTATUS>, action is GET  (at_curl_http_client.c:504)

00028952: 2022-09-25T01:02:09:511445 [COMMUNICATION   ]T:  Clearing (if there is) curl old custom request  (at_curl_http_client.c:950)

00028952: 2022-09-25T01:02:09:511445 [COMMUNICATION   ]T:  calling user pre submit callback  (at_curl_http_client.c:1960)

00028952: 2022-09-25T01:02:09:511445 [COMMUNICATION   ]T:  user pre submit callback returned with status 0  (at_curl_http_client.c:1964)

00028952: 2022-09-25T01:02:09:511445 [COMMUNICATION   ]T:  preparing response structure; body will be written as dynamic string  (at_curl_http_client.c:1428)

00028952: 2022-09-25T01:02:09:912486 [COMMUNICATION   ]T:  http response code is 200  (at_curl_http_client.c:1186)

00028952: 2022-09-25T01:02:10:127510 [SERVER          ]T:  going to connect using connection string <ssl=1;HiveServerType=2;Driver={Cloudera ODBC Driver for Apache Hive};HOST=10.51.2.44;PORT=10000;Schema=hive_lz;AuthMech=3;UID=hive;PWD={****};>  (hive_odbc_client.c:374)

00028952: 2022-09-25T01:02:10:546553 [INFRASTRUCTURE  ]T:  AR_ODBC_DRIVER_FUNC->ar_SQLDriverConnect returned -1  (ar_odbc_func.c:1117)

00028952: 2022-09-25T01:02:10:546553 [SERVER          ]T:  RetCode: SQL_ERROR  SqlState: HY000 NativeError: 1160 Message: [Cloudera][DriverSupport] (1160) Cannot enable SSL for the connection when connecting to a server that has not enabled SSL. If the server has SSL enabled, please check if it has been configured to use a SSL protocol version that is lower than what is allowed for the connection. The minimum SSL protocol version allowed for the connection is TLS 1.2. [1022502]  (ar_odbc_conn.c:584)

The logs confirm that the HDFS connection worked this time, but not the Hive connection failed.

We verify the Hive connection following the same method as before.

1. Ping test:

In a command line, we execute:

ping 10.51.2.44

Where 10.51.2.44 is the IP address of the destination server. 

 Result:  PASS

2. Port Test

This time we use PowerShell, but you can use telnet as well.

We will use port 10000.

In PowerShell, we execute:

Test-NetConnection -ComputerNamer 10.51.2.44 -Port 10000

Where 10.51.2.44 is the IP address of the destination server. 

Result: PASS

3.  ODBC Test

We will test the ODBC connection from the Qlik Replicate server:

Result: Pass

4. Review the Hive connection string

Locate the Hive connection string in the Qlik Replicate log and compare it with the DSN setup.

        ssl=1; HiveServerType=2;Driver={Cloudera ODBC Driver for Apache Hive};HOST=10.51.2.44;PORT=10000;Schema=swathi_lz;AuthMech=3;UID=hive;PWD={****};

The log indicates that we are using SSL.

But as we review the Hive DSN Setup, we can see that we have SSL unchecked:

Result: Everything matched other than ssl=1.

Let’s review and fix the endpoint settings in Qlik Replicate and perform the test connection by removing the internal parameter of ssl=1. 

But what if we receive different error messages?

Generally, driver issues can lead to blockers for Hive connections. If you locate a different error in the UI or the log files, research these errors using either Google or our knowledge base here in the Community, as fixes may already exist. 

Environment:

Qlik Replicate 
Hadoop Target

In some cases when Replicate can't read from the Staging Folder of a LogStream task for whatever reason (corrupted folder, lack of disk space etc), there could be difficulties to resume the LogStream task after the initial issue is solved.

You might see errors like the below when trying to resume from timestamp:

[UTILITIES ]E: Failed to write to audit file  <audit_folder directory>
[UTILITIES ]E: Timeout while waiting to get data from audit file [1002521] (at_audit_file.c:637)

[UTILITIES ]E: Error reading audit batch [1002509] (at_audit_file.c:679)

Environment

• Qlik Replicate 2021.11 (not exclusive)
• Linux RHEL / Windows 

Resolution

1. Stop all LogStream and Replication tasks
2. Kill the replicate sessions and process as the audit file is being locked by the process
3. Rename the audit folder of the problematic audit file (the folder is the one described under the endpoint settings: "Staging Folder" in the Replicate UI)
4. Resume LogStream task from timestamp (a few hours before the initial error), then resume replication tasks from the same timestamp 
5. If not solved, a reload of the task will be needed

Cause 

Usually, the Replicate process (repctl) is locking the audit file that was being written/read while the issue occurred.

While running Qlik NPrinting Tasks, many reports are generated. However, the setting for Days to Keep / Reports to Keep seems to be ignored.

Environment:

Qlik NPrinting all versions

The first thing to consider is that Qlik NPrinting generates one report for each Newsstand user. For this reason, there will be one file for each user, and not "just one", in the Qlik NPrinting Application Data folder. Those reports may be absolutely identical. 

In that sense, the "report to keep" setting does not apply here, and should be considered as "report to keep per user". There is currently an improvement at R&D. Check improvement on days to keep in Nprinting for details. In addition, see Publish task "Reports to Keep" does not work during first 24 hours.

As for the setting apparently being ignored, by default runs the check to delete old reports once every 24 hours. If no new report has been run in the meantime, the old reports will not be deleted, even if more than one day has passed.

Should there be a feeling that the periodic check is not run, the settings can be enforced:

1. Stop the Qlik NPrinting services Proper Order to Restart Qlik NPrinting Services
2. Navigate to and open  C:\Program Files\NPrintingServer\NPrinting\Scheduler\scheduler.config
3. Add the below lines before the </appSettings> closing tag
   

   <add key="cleanup-period" value="1800" />
   <add key="cleanup-period-files" value="43200" />​

4. Restart the services

The first setting is the recurrence in seconds (default: 30 minutes) for the task that will check for reports in the newsstand and unlink the older ones.
The second setting is the recurrence in seconds (default: 24 hours) for the task that will scan and remove the actual files, after checking that the conditions about days and reports to keep, plus the presence of newer reports that supersede them, are met. In this case, we would change the default value to a shorter time (43200 seconds, 12 hours) to make sure the task is run more frequently.

Qlik Sense Util comes bundled with Qlik Sense Enterprise on Windows. It is able to assist in the backing up process to help with the manual process.

Key elements that need to be backed up are: 

• the certificates used by Qlik Sense for internal communication
• the Repository Database used to store meta-data about the Qlik Sense site
• the applications used by the Qlik Sense site
• the Extensions, thumbnail images, etc used by Qlik Sense apps

Other options components can include:

• Logs of activity on the site
• Supplemental material used by the Qlik Sense site (e.g. QVDs, Excel files, etc)

By using the QlikSenseUtil tool, an administrator can back all of these up and configure the tool to be integrated in a silent, incremental backup policy.

How to get started with QlikSenseUtil

1. Locate the QlikSenseUtil tool
   
   
   • Default location: C:\Program Files\Qlik\Sense\Repository\Util\QlikSenseUtil\QlikSenseUtil.exe
   • Custom path example: Drive:\InstallationPath\Repository\Util\QlikSenseUtil\QlikSenseUtil.exe
     
     
2. In Notepad or any text editor of your choice, construct the desired command line syntax for the backup.
   
   
   • A sample command:
     

     C:\"Program Files"\Qlik\Sense\Repository\Util\QlikSenseUtil\QlikSenseUtil.exe -backup -databaseHostname="FQDNofTheDatabase" -databasePassword="SuperUserPassword" -path="Drive:\BackupLocation" -rootPath="\\ServiceCluster\Path"​

   • For a full listing of the flags possible, consult later in this article or the Readme.txt in the QlikSenseUtil directory.
     
     Note: Executing a backup will stop Qlik Sense services, so only execute this tool when downtime is acceptable
     Note: Executing as the Qlik Sense service account is recommended since the client certificate used by Qlik Sense is only accessible to the service account
     Note: For silent backups, do remember to use the -f flag
     Note: Logs for this tool will be written to %USERPROFILE%\AppData\Local\Temp\logs for the account executing the tool
     
     
3. Once the command is written out, launch a command prompt and paste in the command
4. Observe the files backed up to the path specified in the path flag
   
   

Video Walk-through:

Flags:

backup: specifies a backup operation (mandatory)
path: path to the folder where to store the backup (mandatory)
certificatePassword: password for protecting the certificates. If not specified then the certificates will not be backed up
databaseHostname: Hostname where the database is running (mandatory)
databasePassword: Superuser or postgres account password (mandatory, if password was configured)
databasePort: port number used by the database)
f: silent backup
h: help

To restore your environment, see Backup and restore Qlik Sense Enterprise on Windows.

Related Content:

• Qlik Sense Utility - Functions and Features 
• Backup and restore Qlik Sense Enterprise on Windows 

Three requirements need to be met in order to allow Anonymous users access to the Hub:

• The product must not be Qlik Sense Business or Qlik Sense Enterprise SaaS.
• The license must support anonymous access, see Which Qlik Sense Enterprise licenses support anonymous access?
• Proxy must be configured to allow Anonymous users
• A Stream dedicated to anonymous users must be created 

Useful information:

• Users who access Qlik Sense anonymously are identified as NONE\anonymousd9e61933-a7e5-4836-8540-5b137a600e69, where the GUID is a unique identifier.
• To create a license rule, granting login passes to anonymous users you can use two identifiers:
  • userDirectory=NONE 
  • user.IsAnonymous()

Configure the Proxy to allow Anonymous users

By default, anonymous access is disabled. The steps provided require a restart of the Proxy service after completion. 

1. Open the Qlik Sense Management Console.
2. Choose the Virtual Proxy to be used for anonymous access
3. Click Edit.
4. In the Properties menu (right side) choose Authentication
5. From the Anonymous access mode drop-down select Allow anonymous users
   
   
   
   

Set up a license rule 

Anonymous users will need to have a license rule available for them which gives them either an Analyzer Capacity License or a Login Access Token. The instructions in this article will focus on Analyzter Capacity Licenses. 

1. Open the Qlik Sense Management Console.
2. Navigate to License Management 
3. Click Analyzer capacity rules 
4. Click Create new 
5. Give the new rule a Name (mandatory) and Description (optional) 
6. Create one of two possible rules:
   1. In the Basic settings, select
      user: userDirectory =
      value: NONE
      
   2. In the Advanced settings (see Fig 2), provide the condition:
      user.IsAnonymous()
      
      Fig 2

       

7. Click Apply

Set up a Stream for anonymous access

You can use the default Everyone stream, which has already been set up for anonymous access, or create your own. 

We will create two rules. One to allow logged in (authenticated) users access and publishing permissions. One to allow anonymous user access, but no publishing permissons. Note that based on your requirements, this may need to modified. 

1. Go to the Qlik Sense Management Console
2. Go to Manage Content and Streams
3. Click Create New
4. Name your new Stream
5. Click Security Rules 
6. Click Create associated rule (see Fig 2) 
   This will be our "Everyone (anonymous) can read the stream." rule.
   
   Fig 3
7. Provide a Name (mandator) and Description (optional) 
8. In Basic only select Read 
9. In Advanced define
   Condition: user.IsAnonymous()
   Context: Only in hub
   
   See Fig 4. 
   
   Fig 4

    

10. Click Apply 
11. Click Create associated rule (see Fig 2)
    This will be our "Everyone (logged in) can access this stream and publish." rule.
12. Provide a Name (mandator) and Description (optional) 
13. In Basic only select Read and Publish.
14. In Advanced define
    Condition: !user.IsAnonymous()
    Context: Both in hub and QMC
15. Click Apply

Test!

We are now ready to test access. 

1. Go to the Qlik Sense Hub (hosted by the Virtual Proxy you have configured)
2. If you are logged in, log out.
   
   
   
   
3. Our new Anonymous stream is now avaiable.

Getting data out of Qlik Sense Enterprise SaaS, and distributing it to different users in formatted Excel, has been a manual task until now.

Thanks to the release of Qlik Application Automation, it is now possible to automate this workflow by leveraging the connectors for Office 365 - specifically Microsoft SharePoint and Microsoft Excel. 

Here I share two example QAA workspaces that you can use and modify to suit your requirements. 

Video:

Considerations

• QAA cannot currently attach files using the Mail block,  instead this approach distributes a SharePoint link.
• QAA has a limit of 100,000 rows when getting data out of a Qlik Sense straight table object.
• The On-Demand example uses an extension in QSE SaaS to send data to the Automation. An update to the Qlik Sense Button object is expected soon, which will provide a native way to pass selections to an Automation.

Example 1 - Scheduled Reports

1. Download the 'Scheduled Report.json' file attached to this document.
2. Create a new Automation in QSE SaaS, give it a name, and then upload the workspace you just downloaded by right clicking in the editor canvas, and selecting 'Upload workspace'.
3. Select the 'Create Binary File (Personal One Drive)' block, select 'Connection' in the block configurator to the right, and then create your connection to Microsoft SharePoint.
4. Select the 'Get Straight Table Data' block. Under 'Inputs' in the block configurator, lookup your the App Id, Sheet Id, and Object Id for the relevant QSE SaaS table you wish to output.
5. Select the 'Create Excel Table With Headers' block, select 'Connection' in the block configurator, and then create your connection to Microsoft Excel.
6. Select the 'Send Mail' block. Under 'Inputs' in the block configurator update the 'To' to reflect the addresses you wish to deliver to.
7. With the 'Send Mail' block still selected, select 'Connection' in the block configurator and add your Sender details.
8. To test, Save and then Run the Automation
9. If you receive any warnings or errors, navigate to the relevant blocks and ensure your Connection is selected in the block configurator. 
10. Select the 'Start' block. Under 'Inputs' in the block configurator, change Run Mode to Scheduled and define your required schedule. 

Example 2 - On-Demand Reports

Note - These instructions assume you have already created connections as required in Example 1.

1. Download the 'On-Demand Report v3.json' file attached to this document.
2. Download and install the 'qlik-blends' extension. See: 
   https://github.com/rileymd88/qlik-blends/files/6378232/qlik-blends.zip
3. Create a new Automation in QSE SaaS, give it a name, and then upload the workspace you just downloaded by right clicking in the editor canvas, and selecting 'Upload workspace'.
4. Ensure your Connections are selected in the block configurator for each of the following blocks, 'Create Binary File (Personal One Drive)', 'Create Excel Table With Headers', 'Add Rows To Excel Worksheet Table (Batch)', 'Create Sharing Link', and 'Send Mail'.  Save the Automation.
5. Select the 'Start' block and ensure Run Mode is set to Triggered. Make note of the of URL and Execution Token shown in the POST example. 
6. Open your chosen QSE SaaS application, and Edit the Sheet where you wish to add a Button to trigger an On-Demand report. 
7. Under 'Custom Objects' look for 'qlik-blends' from the Extensions menu and drag this into your Sheet.
8. Under the 'Blend' properties to the right, add-in your POST webhook URL and Token as noted in Step 5.
9. We will now add three measures to the 'qlik-blends' object. It is important you add them in the order described.  Add the first measure, using the following function in the expression editor: GetCurrentSelections()
10. Add the second measure, using the following function DocumentName()
11. The final measure will be the Object ID of the table you wish to use. To find the Object ID, select 'Done Editing'.  Then right click on the table, select 'Share', select 'Embed', then look for the Object ID under the preview. Copy this value, go back into Editing mode and paste this as your third measure value. 
12. With the 'qlik-blends' object selected, under Form select 'Add items'. For 'Item type' select Text. Under default value you can choose to add a default email address. For 'Label' and 'Reference'  type 'Email'. It is critical that Reference is updated to 'Email'.  Turn 'Required input' on. 
13. You can change the Appearance properties to suit your preferences, such as updating the Button label and message, enabling Dialog, and changing the Color under Theme.
14. Back in the Automation, under the Start Block. Set  'Run asynchronously' = yes to allow multiple requests to run at the same time (This will also increase the max run time from 1min to 60min)
15. Once happy, test the On-Demand report by entering an email and clicking the button.

This On-Demand Report Automation can be used across multiple apps and tables.  Simply copy the extension object between apps & sheets, and update the Object ID (Measure 3) for each instance. 

Environment

• Qlik Application Automation 
• Qlik Cloud 
• Microsoft Office 365

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Monitoring App reload fails with:

Error message: Error: QVX_UNEXPECTED_END_OF_DATA: HTTP protocol error 401 (Unauthorized): Requested resource requires authentication.

The error happens when the Qlik Sense services account does not match the account used in the reload task.

Resolution:

The data connections must be updated accordingly with the Qlik Service User ID and Password.

• Open the Qlik Sense Management Console
• Navigate to Data Connections 
• Locate monitor_apps_REST_ data connection
• Click Edit
• Enter the correct User ID and Password (as seen in Fig 1)
• Save the changes.

Fig 1