The below error is logged in the QlikView Server Event logs:

Error    System: file system LastWriteTimeException: Last write time for \ failed: LastWriteTimeException \ failed: boost::filesystem::last_write_time: The system cannot find the file specified: "\\servername\USA\QLIKVIEW\EXT\Document\zoomToFit\Definition.xml ": no such file or directory    550365d6-ae70-44a2-9ea8-aace5b5b8d38

For information on QlikView logs, see QlikView Services and Log Guide 

Environment

• QlikView 12.50

Resolution

Check the extension name (in red above) to make sure it is installed properly .

Starting at Qlik Sense Enterprise on Windows May 2021, the bundled PostgreSQL has been upgraded to version 12.5.

However, PostgreSQL 12.5 will only be deployed during a fresh installation of Qlik Sense Enterprise on Windows May 2021. This means that, if you are upgrading to Qlik Sense Enterprise on Windows May 2021, PostgreSQL will remain on 9.6.

For many organizations, running on the latest supported PostgreSQL version is a security requirement. To achieve this:

• Move Qlik Sense database to standalone PostgresSQL database in which case you will have control of which PostgreSQL version is deployed as long as it is supported by the system requirements
• Continue to use the bundled PostgreSQL with version 12.5 (see the process below)

Content:

• Step 1: Upgrading your Qlik Sense site
• Step 2: Backing up your Qlik Sense site
• Step 3: Uninstall Qlik Sense on the central node
• Step 4: Install Qlik Sense Enterprise on Windows May 2021 on the central node
• Step 5: Restoring your Qlik Sense site

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

This process requires a full reinstallation of the product. Despite the fact that a backup is being taken as part of the process, it is highly recommended to have a second backup plan in place such as a Virtual Machine snapshot and/or a Server Backup.

It is highly recommended to test this process in a test environment to get familiar with it.

Step 1: Upgrading your Qlik Sense site

The first step is to upgrade your environment to Qlik Sense Enterprise on Windows May 2021 following the steps and recommendations provided on this link.

Once the upgrade is done make sure your Qlik Sense site is completely operational.

Step 2: Backing up your Qlik Sense site

At this point, you have an operational Qlik Sense site running on Qlik Sense Enterprise on Windows May 2021, however, the bundled PostgreSQL is still on version 9.6.

The next step will be to backup your entire Qlik Sense site following these instructions (including the certificates) . The backup is essential as it will need to be restored later on.

Step 3: Uninstall Qlik Sense on the central node

You will now need to uninstall Qlik Sense from the central node following these instructions.

During the uninstall:

• Have all rim nodes stopped.
• Don't check the box Remove Qlik Sense demo apps, certificates, and data folders.
• After uninstall and before reinstall rename C:\programdata\qlik to C:\programdata\qlik.old and rename C:\program files\qlik to C:\program files\qlik.old (if you changed it on another drive adjust accordingly)

Step 4: Install Qlik Sense Enterprise on Windows May 2021 on the central node

Now that Qlik Sense Enterprise on Windows May 2021 is uninstalled on the central node, you will reinstall it as a result will deploy a bundled PostgreSQL 12.5. Instructions available here.

• select the same host name and database settings as before
• The file share can point at a temporary one since you will take the original one again after restoring the QSR database in step 5.

Do not check the box Start theQlik Senseservices when the setup is complete at the end of the installer.

Step 5: Restoring your Qlik Sense site

You now have a clean Qlik Sense Enterprise on Windows May 2021 deployed on your central node with PostgreSQL 12.5. You now need to restore your environment to retrieve all your configurations and apps.

Please follow the Restoring a Qlik Sense site (including the certificates).

Note: While restoring the database backup you will most likely receive the following error which can be ignored. This error is caused by the version discrepancies between the pg_dump that made the dump file and the pg_restore that's restoring it - in example files coming from PostgreSQL version 9.6 vs files coming from PostgreSQL version 12.5. QSR backup taken and restored with the same version of PostgreSQL will not produce that error.

pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 3; 2615 2200 SCHEMA public postgres
pg_restore: error: could not execute query: ERROR: schema "public" already exists
Command was: CREATE SCHEMA public;

pg_restore: warning: errors ignored on restore: 1

Once the environment is restored, you should be able to start your central node and rim nodes successfully.

Environment

Qlik Sense Enterprise on Windows May 2021 and later

You can set the audit trail retention size and age using the CLI in Qlik Enterprise Manager.

The command: aemctl.exe audit_trail control [--age hours] [--size megabyte]

 See Setting the audit trail retention size and age for details.

Previous documentation versions of Qlik Enterprise Manager may refer to an incorrect syntax. Always use the most recent guide.

Scenario:

• An MSSQL to Snowflake via Logstream task
• Apply changes and store changes are both enabled
• Store before and after on update settings are used

Records are missing from the __CT table.

Resolution

An enhancement was introduced in Qlik Replicate (version 2022.11), adding a feature which forces Qlik Replicate always to write the change table entry. 

Enable the feature in the task settings:

1. Open the task settings
2. Click More Options
3. Add the following feature flag: writeEqualBeforeAndAfterImagesToChangeTable
4. Set it to On
   
   

Environment

Qlik Replicate 

Apply latency increases in a task. The target endpoint Snowflake Azure has a custom policy defined meant to mask/hide values for certain fields in the target. LOB support in the task is disabled. 

The following is logged:

00005856: 2023-04-02T00:08:37 [TARGET_APPLY ]I: Column 'Field_Name' is unsupported in table def 'table_XX' since the LOB support is disabled (metadatamanager.c:2632)

Resolution

The target table has a masking policy defined. This policy is not applied by Qlik Replicate.

Example: Field_Name VARCHAR(30) NOT NULL WITH MASKING POLICY #unknown_policy,

If there is masking policy in the target table, Qlik Replicate will consider it as a LOB column. Therefore, when LOB is support is disabled, we see the mentioned warning.

Field_Name is part of the Primary key. To prepare any update statement the PK columns, values are needed. Without them, Qlik Replicate cannot prepare the update statements.

If Qlik Replicate creates the table without a masking policy in the target table, then disabling LOB support will not impact this table to replicate all columns.

Environment

Qlik Replicate 

A Qlik Replicate task has stopped due to a Connection error at Kafka Target endpoint:

00003824: 2023-04-13T08:24:16 [TARGET_APPLY ]E: Failed to get Kafka metadata: Local: Broker transport failure. _TRANSPORT [1020401] (kafka_client.c:432)
00003824: 2023-04-13T08:24:16 [TASK_MANAGER ]E: Failed while preparing stream component 'st_0_INT_Bootstrap_Kafka_Target'. [1020401] (subtask.c:853)
00003824: 2023-04-13T08:24:16 [TASK_MANAGER ]E: Cannot initialize subtask [1020401] (subtask.c:1297)
00003824: 2023-04-13T08:24:16 [TARGET_APPLY ]E: Stream component 'st_0_INT_Bootstrap_Kafka_Target' terminated [1020401] (subtask.c:1565)
00003824: 2023-04-13T08:24:16 [TARGET_APPLY ]E: RDKAFKA - 3 - ERROR: [thrd:app]: QlikReplicate/2022.11/kafka#producer-1: sasl_ssl://URL:1921: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed: broker certificate could not be verified, verify that ssl.ca.location is correctly configured or root CA certificates are installed (add broker's CA certificate to the Windows Root certificate store) (after 82ms in state CONNECT) [1022601] (kafka_client.c:236)
00003824: 2023-04-13T08:24:16 [TARGET_APPLY ]E: RDKAFKA - 3 - ERROR: [thrd:app]: QlikReplicate/2022.11/kafka#producer-1: sasl_ssl://URL:9093/bootstrap: SSL handshake failed: ssl\statem\statem_clnt.c:1921: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed: broker certificate could not be verified, verify that ssl.ca.location is correctly configured or root CA certificates are installed (add broker's CA certificate to the Windows Root certificate store)

Resolution

Add broker's CA certificate to the Windows Root certificate store. Once this is done, put the cert file on the Qlik Replicate installation server and refer to the .pem at the CA path field.

After updating the EP settings with the above-mentioned, restart the task or stop and resume so the changes will take effect. First, test the connection using the test connection button.

Environment

Qlik Replicate 

With Qlik Application Automation, you can get data out of Qlik Cloud and distributing it to different users in formatted Excel. The workflow can be automated by leveraging the connectors for Office 365, specifically Microsoft SharePoint and Microsoft Excel. 

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

Content:

• Considerations
• Example 1: Scheduled Reports
• Example 2: On-Demand Reports
• Environment

Video:

Considerations

• This example is built on distributing a SharePoint link. It is also possible to use attachments with the Mail block (see Creating a Qlik Reporting Service report).
• Qlik Application Automation 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.

When trying to use Qlik Data Transfer for the first time after a correct installation, you might have the below white screen:

Having a white screen basically means one of the Qlik DataTransfer micro service is not started and/or not working. This can be checked in the Windows Event Application (Source: Qlik Sense Service Dispatcher) or in the Qlik DataTransfer logs (C:\ProgramData\Qlik\DataTransfer\Log).

In the \DataUploadService logs you will see this error message:

localhost 6.0.0 Global INFO Responding certificates after reading it from defined location.
localhost 6.0.0 Global ERROR Unable to unlock the ReloadService, cannot continue.
localhost 6.0.0 Global ERROR Exception: Error: Unable to unlock the reload service.

Resolution

This error message is happening directly after the step of reading certificate:

INFO Responding certificates after reading it from defined location.

Verify the certificate:

Verify what certificates you have listed in the MMC console.

1. Are no certificates listed?
   
   
   
   

2. A group policy or other system security settings may have prevented certificates from being installed. Follow the Reset certificates steps found in the second half of the article after lifting potential restrictions on the account or machine which previously prevented the certificates from being installed. 

3. If you see some Qlik DataTransfer duplicate certificates (fig 1), duplicates must be deleted.
   
   fig 1
   
   
4. Delete the two duplicates (which have no Friendly Name listed. 
5. Restart the Qlik DataTransfer service.

Are other Qlik Products installed on the same server?

Installing Qlik Sense Enterprise on Windows (Desktop or otherwise) will also lead to compatibility issues, including certificate mismatches.

1. If the other product was previously uninstalled, the certificate may still be present.
2. Verify in the MMC console and navigate to Certificates (Local Computer) --> Personal -- Certificates to see if another QlikClient certificate is installed.
3. Remove it.
4. Then follow the Reset Certificates steps found below.

Are you using a Proxy?

A proxy system variable may be set in Windows. Example: https_proxy=http://PROXY:80 

Qlik Data Transfer does not support the use of a proxy. Delete the Windows variable.

Reset Certificates 

If only Qlik DataTransfer is installed on the machine, do the following:

1. In Windows Services, stop the Qlik DataTransfer service.

2. Navigate to C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate and delete the certificates there.
   
   

3. Navigate to C:\Program Files\Qlik\DataTransfer\DataUploadService\install-utils.

4. Run Remove-Certificate.ps1 in PowerShell.

5. Delete the following folder: C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate
   

6. Start the Qlik DataTransfer service.

7. Navigate to C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate and confirm the following files are present:

   • client.pfx

   • server.pfx

If Qlik DataTransfer and Qlik Sense Enterprise on Windows are installed on the machine, do the following:

1. In Windows, Services, stop the Qlik DataTransfer service.

2. Navigate to C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate and delete the certificates in the folder.
   
   

3. In the Windows Certificate Store, delete the following certificates:

   • Local Computer > Personal > QdtClient

   • Local Computer > Trusted Root Certification Authority > <hostname.domain> or <hostname>

   • Current user > Personal > QdtClient

   Alternatively, you can run Remove-Certificate.ps1 in PowerShell as the administrator.
   
   

4. Run Configure-Service.ps1 in PowerShell as the Qlik Sense services user.

   1. For the first input dataTransferCertificatePath, enter C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate.

   2. For the second input qsefwPresent, enter Yes.

5. Navigate to C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate and confirm the following files are present:

   • root.pfx

   • client.pfx

   • server.pfx

6. Restart the Qlik DataTransfer service.

Related Content 

Installing and Using Qlik DataTransfer  
Troubleshooting Qlik DataTransfer 

Environment

Qlik Data Transfer any release

The distribution of QlikView apps from QlikView Distribution Service to Qlik Cloud fails with the error "TestCloudLicense: Failed - Unauthorized. Failed to retrieve qv_nodes tag."

Environment

• QlikView 
• Qlik Cloud 

Resolution

• The license used in Qlik Cloud is missing the QV_NODES tag, which allows the access to QlikView apps from Sense Deployments. For QlikView to distribute to a Qlik Cloud tenant,  the tag must be present in the tenant license.

Please, reach out to your account manager to have that fixed.

• This issue could also occur if there are missing configuration entries in he QVDistributionService.exe.config  file, refer to the following article QlikView Distribute to cloud fails: The type initializer for System.IdentityModel.Tokens.Jwt.JsonExtensions threw an exception.

Your Qlik Cloud license includes information on what licenses and features are enabled for you. You will receive a list of all your enabled features in your original license email and we always recommend to store the email for future reference.

However, you can also call the License APIs in your browser and obtain information on what features are included in your license from there.

Resolution

1.  Access your tenant's URL and authenticate
   
   
2. Append /api/v1/licenses/overview to the URL
   Example: https://mytenant.myrg.qlikcloud.com/api/v1/licenses/overview
   
   
3. The information will be visualized in the browser
   
   
   • Most browsers will show the raw JSON format 
     
     
     

      

   • Other browsers (such as Firefox) have a built-in JSON visualizers:
     
     
     
     
4. Search for the key that you are expecting to find and the values associated with it to confirm that the feature is enabled:
   
   

   {"name":"qvNodes","valid":"./.","values":{"count":3}},

   {"name":"reportingService","valid":"./.","values":{"quantity":1000,"value":""}}]​

Environment

Qlik Cloud 

Testing the connection to an AWS RDS hosted Mariadb database fails with:

SYS-E-HTTPFAIL, No MySQL ODBC Unicode Driver version x.x or above is installed..
SYS,GENERAL_EXCEPTION, No MySQL ODBC Unicode Driver version x.x or above is installed.

Resolution

Verify that the Qlik Replicate documentation was followed correctly and that the /etc/odbcinst.ini file contains an entry for MySQL. See Driver prerequisites | Qlik Replicate Help.

If a new driver was installed, it may have overwritten a previous entry or wrongly added a new one.

Per Qlik documentation:

[MySQL ODBC 5.3.13 Unicode Driver]
Driver = /usr/lib64/libmyodbc5w.so
UsageCount = 1

Per the driver installation:

[MySQL ODBC 5.3 Unicode Driver]
Driver=/usr/lib64/libmyodbc5w.so
UsageCount=1

Remove .13 in the .ini file to resolve this.

Environment

Qlik Replicate 

Some script logs are not transferred to Archive log Folder.

Storage Locations:

Qlik Sense log folder:

C:\ProgramData\Qlik\Sense\Log\Script
Log names consist out of the AppID and a year, date, and timestamp.

Archived log Folder:

 \\SERVICECLUSTER-SHARE\ArchivedLogs\NodeName\Script
Log names consist out of the AppID and a year, date, and timestamp.

Environment:

• Qlik Sense Enterprise on Windows, all versions

Resolution:

By design, not all script logs are transferred to the Archived logs folder. Reloads executed from the hub are not transferred. 

1. When reloading data in app via hub, Script log will be left in Script log folder C:\ProgramData\Qlik\Sense\Log\Script

2. When reloading data via QMC/task, Script log will be transferred to Archived logs folder \\SERVICECLUSTER-SHARE\ArchivedLogs\NodeName\Script

Related Content:

• How to find the Script (Reload) logs in Qlik Sense Enterprise

Security Rules can be configured to allow end-users to reload tasks directly from the Qlik Sense Hub. This way the users who don't have access to Qlik Sense Management Console can run the tasks that are created for the app directly from the hub.

Environment

• Qlik Sense February 2021 & later (For "Manage reload tasks": start/stop existing tasks from the hub)
• Qlik Sense May 2021 & later (An addition to "Reload": create tasks from the hub)

Security Rule examples are provided as-is. Further customization cannot be supplied by Qlik Support and we recommend engaging with our active community in the Qlik Sense Management forums for further assistance. 

Requirements and Considerations

• By default, a user will have Read and Update permissions on Apps they own, whether they are Published or not. 
• If you intend to give users permission to reload a published App they do not own, a separate security rule will be necessary to enable Read and Update permissions on the App. 
• A Professional License. Analyzer licenses will only be able to view tasks, even with the security rules in place. 
• By default, all users have access to the required HubSection_Task. This is the starting point to allow users to reload from the hub. If custom rules have been implemented that block access to HubSection_Task, this needs to be lifted or customised.

Note: Too many tasks run in parallel by users can cause a performance impact. 

Set up the Security Rules:

1. Open the Qlik Sense Management Console
2. Go to Security Rules in the left side menu
3. Click Create New 
4. Set up either a for only managing existing tasks only or b for creating new tasks and managing existing tasks:
   
   
   1. Start and Stop existing Reload Tasks only
      
      Name: Reload Access from Hub (example) 
      Description: Allows users to reload apps from the hub  (example) 
      Resource filter: ReloadTask_* (Can be chosen from the dropdown menu next to the box)
      Actions: Read, Update 
      Conditions: Specify your user or group or role.
      
      
   2. Create a new Reload Task and launch it as well as manage existing tasks
      
      Name: Reload Access from Hub (example) 
      Description: Allows users to create reloads from the hub  (example) 
      Resource filter: ReloadTask_* (Can be chosen from the dropdown menu next to the box)
      Actions: Read, Update, Create 
      Conditions: Specify your user or group or role.
      
      
5. Apply both rules

The specified users can now right-click on the hub to access the Management Reload Task (rule a) or/and Reload option (rule b). See Fig 1.

Fig 1

Clicking Reload to initiate the reload and open the App in a new tab.

Clicking Manage reload tasks to access all available reload tasks for this App. Tasks can then be started (Fig 2) or stopped (Fig 3)from this menu.

Fig 2

Fig 3

Additional Notes:

• Giving access to the Apps will always expose the Manage Properties option.
  
  This can be mitigated by modifying the existing ReadCustomProperties rule to fit your needs. However, this will not hide the Manage Properties option. 
  
  
• Giving Update permissions to users allows them to edit the App's name, description, and thumbnail. This is working as expected. 

This article is meant to get users starting on the Oauth connector in Qlik Application Automation.
This connector is meant for advanced users to platforms where we did not (yet) build a dedicated connector for.
The connector makes use of the authorization code flow of Oauth2. The authorization code flow is well explained on the following link: https://oauth.net/2/grant-types/authorization-code/

Limitations

• This connector will work for most OAuth2 flows. In cases where there's additional fields to be sent such as additional query parameters in the authorize request, this connector will not work.
• For the list endpoints other than those listed below The solution is to implement paging at the automation level. This is well explained in the following article.: https://community.qlik.com/t5/Knowledge/How-to-implement-pagination-using-Call-Url-block-in-an/ta-p/1879458
  • raw API list request - offset based paging
  • raw API list request - page number based paging.
  • raw API list request - cursor token based paging
  • raw API list request - cursor URL based paging
• If the cursor token or cursor URL is returned in the response header instead of the response body, the cursor URL and cursor token endpoints do not work.
• The list blocks won't work if the business data in the API response is not enclosed in a JSON key.

How to connect

First start by looking for the connector "OAuth2". When you click on connect it requests the following input parameters:

• Base URL - This should be the base of the URL you will be making REST calls to. We recommend providing this as much as possible as it will prevent making calls to other URL's.
• Authorize URL - Can usually be obtained from the documentation of the platform you're attempting to connect to.
• Access Token URL - Can usually be obtained from the documentation of the platform you're attempting to connect to.
• Refresh Token URL - Can usually be obtained from the documentation of the platform you're attempting to connect to. Most of the time this is the exact same as the Access Token URL.
• OAuth Client ID - Will have to be created in the platform you're connecting to.
• OAuth Client Secret - Will have to be created in the platform you're connecting to.
• OAuth Scopes - Obtain from documentation.

When all of this is provided and you click the Save button, it will open a popup taking you to the login screen where you will be prompted to provide consent. Your connection is now ready to be used.

How to use in an automation

When selecting the connector in an automation you will notice Raw API Request block. This block has the following input variables:

• Path - This needs to be relative to the Base URL you provided when connecting.
• Method - Enum choice between GET, POST, DELETE, PATCH or PUT.
• Query Parameters - Here you can provide a JSON object and the key/values will be added to the path as query parameters.
• Request Body - A JSON object can be provided for POST, PATCH or PUT operations that will be sent as request body.
• Headers - JSON object and these key/values will be added as headers to the request.

Apart from the above input variables, RAW API LIST blocks have the following input variables

• Page Size Field Name - Name of the page size query parameter.
• Page Size - The desired page size. The maximum value allowed is 200.
• Offset Field Name - Name of the offset query parameter.
• Page Start - The initial value of the Offset Field Name or Page Number Field Name query parameter. It should be either 0 or 1.
  • For offset based pagination: Depending on the page size and the page start the value of the offset parameter for the second page will be calculated. 
  • For Page number based pagination: The page number is either a 1-based or zero-based value. The value will be incremented by 1 to fetch the next page's data.
• Json Path For Output Records - The JSON key's name in the response will be used to parse a portion of the overall JSON returned by the API endpoint. This only returns a parsed VALUE.
• Json Path For Cursor - The JSON key in the API response whose cursor/token value can be used to request the next page of resources. 
• Output Name For Cursor Token - Name of the cursor token query parameter.
• Page Number Field Name - Name of the page number query parameter. 
• Json Path For Cursor Url - The JSON key in the API response, which is effectively a URL, can be used to retrieve the next page of resources. 

An example

The following example will obtain tasks from the Microsoft Todo application. We do not yet have a connector to do this and Oauth is used to obtain the value for the Authorization header.
We first start by obtaining the Authorize URL, Access Ttoken URL and Refresh Token URL. From the Microsoft documentation we can find these at https://docs.microsoft.com/en-us/graph/auth-v2-user. We use the following values:

• Authorize URL: https://login.microsoftonline.com/common/oauth2/v2.0/authorize
• Access Token URL: https://login.microsoftonline.com/common/oauth2/v2.0/token
• Refresh Token URL: https://login.microsoftonline.com/common/oauth2/v2.0/token

The documentation of the Microsoft Graph API  can be found at https://docs.microsoft.com/en-us/graph/use-the-api?context=graph%2Fapi%2F1.0&view=graph-rest-1.0.
We obtain the Base URL: https://graph.microsoft.com/v1.0.

We will have to obtain a client ID and client secret. We can do the registration for an app at https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade. We register a new application, give it the name "Todo App" and set it to only allow accounts from this organizational directory only. For the redirect url the following value needs to be provided: https://connector.qlikcloud.com/callback. Set the platform to Web.

On the next screen you can obtain your Client ID. Copy this value. Click on Add a certificate or Secret and it will take you to a page where you can create a new client secret.
Create one and copy the value that is now visible.

In the left sidebar click on the button API Permissions. Click on Add a Permission and provide the scope Tasks.ReadWrite.

Back to your connector configuration - Provide the client ID and client secret that were obtained and for the scopes provide the following: User.Read Tasks.ReadWrite offline_access openid
Now click on Save and you should be presented with a screen to login.

Using it in an automation

1) Raw API Request block:

Create a new automation and drag the Raw API Request block on to the canvas. Set the path to /me and the method to GET. When you now execute it, you should receive a JSON result containing the keys response, headers and status. Most relevant information should be part of the response.

Next let's obtain a list of tasks. Drag another Raw API request block and put it below the earlier one. Set the path to /users/{$.rawApiRequest.response.id}/todo/lists and method should remain at GET. Now when you execute this, it will return you the lists you keep in Todo.

2) List Blocks: Depending on the type of pagination, we have 4 different List blocks. Therefore, depending on the type of pagination in API, any one of the List blocks should be used for a certain API.

We tested the blocks using four distinct APIs, each with a different pagination implementation.

• raw API list request - page number based paging: Zoho
• raw API list request - offset based paging: JIRA
• raw API list request - cursor token based paging : Google People
• raw API list request - cursor URL based paging : Bitbucket

1. raw API list request - page number based paging: 
   Create new automation and drag the raw API list request - page number based paging block onto the canvas.
   Create a new connection. We used the Zoho API. Please visit the API documentation link for your API to obtain Oauth information and the pagination documentation to obtain pagination information.
   
   
   Below are the input parameter
   
   1. path: If the baseUrl in the connection parameter ends with '/', do not prefix the same character at the beginning of the path in the endpoint input parameter. We are using "Leads" to list the lead in Zoho.
   2. Query Parameters: We haven't used them in the example. Similarly, we can try a variety of other query parameters listed in the API documentation.
   3. Headers: We don't use it because we don't require any further header information.
   4. Page Size Field Name: per_page is the query parameter name used to reduce the amount of data returned in a single API call.
   5. Page Size: The query parameter per_page's value. We made use of 8. If the entered value exceeds 200. We'll set it to 200 in the backend.
   6. Page Number Field Name: Because this is page-based pagination, the page query parameter is 'page'.
   7. Page Start: This is the number that indicates where the page begins. The value should be either 0 or 1. This value will only be used in the first API request; in subsequent calls, it will be increased by one in the backend and used in the above page query parameter name. We have used 1.
   8. Json Path For Output Records: Parse a portion of the JSON returned by the API endpoint. This only returns a parsed VALUE. We have used 'data' in our example.
      
      
2. raw API list request - offset based paging : 
   Create new automation and drag the raw API list request - offset based paging block onto the canvas.
   Create a new connection. We used the JIRA API. Please visit the API documentation link for your API to obtain Oauth information and the pagination documentation to obtain pagination information.
   
   
   Below are the input parameter
   
   1. path: If the baseUrl in the connection parameter ends with '/', do not prefix the same character at the beginning of the path in the endpoint input parameter. We are using "Search" to search the issues
   2. Query Parameters: We utilized the fields query parameter to limit the data returned by JSON Object. Similarly, we can experiment with many additional query parameters listed in the API documentation.
   3. Headers: We don't use it because we don't require any further header information.
   4. Page Size Field Name: maxResults is the query parameter name used to reduce the amount of data returned in a single API call.
   5. Page Size: The query parameter maxResults's value. We made use of 50. If the entered value exceeds 200. We'll set it to 200 in the backend.
   6. Offset Field Name: Because this is offset pagination, the offset query parameter is startAt.
   7. Page Start: This is the offset's starting number. The value should be either 0 or 1 
   8. Json Path For Output Records: Parse a portion of the JSON returned by the API endpoint. This only returns a parsed VALUE. According to the JIRA API docs, we're getting a list of issues from the "issues" key.
      
3. raw API list request - cursor token based paging:
   Create new automation and drag the raw API list request - token based paging block onto the canvas.
   Create a new connection. We used the Google People API. Please visit the API documentation link for your API to obtain Oauth information and the pagination documentation to obtain pagination information.
   
   
   Below are the input parameter
   
   1. path: If the baseUrl in the connection parameter ends with '/', do not prefix the same character at the beginning of the path in the endpoint input parameter. We are trying to list the contactGroups in Google People.
   2. Query parameters: We haven't used them in the example. Similarly, we can try a variety of other query parameters listed in the API documentation.
   3. Headers: We don't use it because we don't require any further header information.
   4. Page Size Field Name: pageSize is the query parameter name used to reduce the amount of data returned in a single API call.
   5. Page Size: The query parameter maxResults's value. We made use of 20. If the entered value exceeds 200. We'll set it to 200 in the backend.
   6. Json Path For Cursor: The JSON key in the API response, the cursor value will be used to request the next page of resources. Use '.' to denote objects within an array. This endpoint block will not work if the cursor URL is returned in the header.
   7. Output Name For Cursor Token: The name of the cursor Query parameter, which will be used to fetch resources for the following page. We used pageToken in this case.
   8. Json Path For Output Records: Parse a portion of the JSON returned by the API endpoint. This only returns a parsed VALUE.
      
      
4. raw API list request - cursor URL based paging
   Create new automation and drag the raw API list request - URL based paging block onto the canvas.
   Create a new connection. We used the Bitbucket API. Please visit the API documentation link for your API to obtain Oauth information and the pagination documentation to obtain pagination information.
   
   
   Below are the input parameter
   
   1. path: If the baseUrl in the connection parameter ends with '/', do not prefix the same character at the beginning of the path in the endpoint input parameter. We are trying to list the commits.
   2. Query parameters: We haven't used them in the example. Similarly, we can try a variety of other query parameters listed in the API documentation.
   3. Headers: We don't use it because we don't require any further header information.
   4. Page Size Field Name: maxResults is the query parameter name used to reduce the amount of data returned in a single API call.
   5. Page Size: The query parameter maxResults's value. We made use of 50. If the entered value exceeds 200. We'll set it to 200 in the backend.
   6. Json Path For Cursor Url: The JSON key in the API response, which is effectively a URL, can be used to retrieve the next page of resources. Use '.' to denote objects within an array. This endpoint block will not work if the cursor URL is returned in the header.
   7. Json Path For Output Records: Parse a portion of the JSON returned by the API endpoint. This only returns a parsed VALUE.

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.

Beginning with QlikView May 2021, the QlikView Publisher no longer installs PDF-XChange and will default to Microsoft Print To PDF. 

How to generate PDF reports on a Windows 2012 server, since Print To PDF is not installed there?

Resolution

Have the PDF X-Change 3.0 installed with a previous version of QlikView. If you begin with 12.60, follow this article.

After PDF X-Change 3.0 has been installed, follow these steps:

1. Stop the QlikView Management Service
   
   
2. Using a administrator Notepad, edit:
     
   C:\Program Files\QlikView\Management Service\QVManagementService.exe.config
   
   
3. Locate the <appSettings> section
    
4. Add the line
   
   <add key="ShowPdfPrinters" value="true" />
   
   
   

    

5. Save the file and start the QlikView Management Service
   
   
6. Open the QlikView Management Console:
   1. Go to System
   2. Go to Setup
   3. Expand the Distribution Services
   4. Choose your Distribution Service
   5. Switch to the General tab
   6. Scroll to the Settings for QDS section
   7. You can now configure the PDF Printer using a dropdown 
      
      
      
      

      Additional third party printers have not been tested. In case of performance or stability issues, install one of the two supported printers (PDF X-Change or Microsoft Print to PDF).

Environment

QlikView May 2021 (12.60) on a Windows 2012 server

Currently, in Qlik Application Automation it is not possible to export more than 100,000 cells using the Get Straight Table Data block.

Content:

• Full Automation
• Steps to set up the variables
• Automation structure

To overcome this limit, the workaround is to export records in batches from the Qlik Sense straight table to the cloud storage platform of your choice. The prerequisite is to have a unique numerical field in your dataset. If you don't have the unique field in your dataset, you can add it using RowNo() function in the load script as shown below. This counts the rows in the dataset.

In this example, we will export data from the Qlik Sense straight table to Dropbox as a CSV file.

You can also find an exported version of this automation and application attached to this article. More information on importing automation can be found here.

Full Automation

Automation Part 1

Automation Part 2

Automation Part 3

Steps to set up the variables

1. vAppId: Variable used to define your app ID.
2. vSheetId: Variable used to define your sheet ID.
3. vTableId: Variable used to define your straight table ID.
4. vFieldName: Variable used to define the field name on which the straight table data should be filtered based on the selection applied using the Select Field Value By Query block.

Automation structure

1. Add the Create Measure block to the automation and configure the Measure Expression parameter by providing an expression that calculates the number of rows in the dataset. In this example, I have added RowNo( ) as a unique field to the dataset, so the expression used is count([RowNo( )]).
2. Add the Get Measure block to get the number of rows in the dataset.
3. Store the number of rows obtained from the previous step in the vNRecords variable.
4. Delete the measure created using the Delete Measure block.
5. Add the vNLoops variable to calculate the number of loops that can be used to export straight table data in batches. Please note the formula used in the variable. Edit it to suit your needs. Change the 10000 value as you want but keep in mind that too many records could exceed the Get Straight Table Data block's 100,000 cells limit.
   
   
   
   
6. The Custom Code block creates a list with items 1 to n where n is the number of loops calculated in the previous step.
7. Add Create File on Dropbox block to create a new CSV file in Dropbox. You can select any other cloud storage connector, just remember to configure the relevant value in the Path parameter. The Qlik Sense straight table data will be exported to this file.
8. Add the Select Field Values By Query block to apply selection to the unique identifier created in the dataset to fetch only one record from the Get Straight Table Data block.
9. Add Write Line To File on Dropbox block to add straight table keys as column headers to the CSV file.
10. Add Loop block to loop over the list created using the Custom Code block.
11. Add Condition block to check if it's iterating over the 1st item, if yes set vRecordsStart variable value to 1, else set vRecordsStart variable value to vRecordsEnd variable. The vRecordsEnd variable represents the last record that needs to be fetched from the straight table during each iteration. Please note the formula used in the variable. The value under the Value 1 parameter in the Multiply formula should match the value provided in the Divide formula of the vNLoops variable.
    
    
    
    
12. Add the Select Field Values By Query block to apply selection to the unique identifier created in the dataset to fetch the records between vRecordsStart and vRecordsEnd variables from the Get Straight Table Data block.
13. Add Write Line To File on Dropbox block within the Get Straight Table Data block which writes each straight table data into the CSV file. Configure it to use the output from the Get Straight Table Data block as the Data parameter.
14. Add Save And Close File on Dropbox block and configure the file parameter to use the CSV file we have created.

Environment

• Qlik Cloud
• Qlik Application Automation 

Before reading this, please refer to the official QlikView Authentication - Qlik Online Help and your specific version for details. 

QlikView allows for a number of 3rd party, custom authentication methods to be implemented, which may leverage an Identity Provider (IdP) of choice. However, many aspects of this integration is limited to best-effort support from Qlik Technical Support. See How and When to Contact the Consulting Team?

By default. QlikView only interacts with Windows using the appropriate APIs in the background, allowing Windows to carry out any authentication attempts and passing that information to the QlikView system.  Custom Users in the Directory Service connector are a second option, which allows QlikView itself to do authentication.

Any other user repository will require external, 3rd party implementations.
 

Environment:

• QlikView 

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

This document includes some possible examples in a QlikView 11 implementation of WebTickets and Header authentication, with examples from .NET, PHP, and LDAP integrations. The examples are provided as is. 

! The document references http://localhost:4730/qtds.asmx, which was a valid URL used in QlikView 10 (no longer supported).
This function has been removed in QlikView 11.

! The document references a WebTicket implementation limitation:
A current limitation is that the QVWS or IIS used in steps 2 and 3 (i.e. the server you collect the ticker from and the server you redirect the user to) must be the same machine.
This limitation no longer applies in the current QlikView 12 and 11.20 versions.