This article offers an example on how to set up a security rule matching to a role which is restricted to seeing only "License Management" in the Qlik Sense Management Console.

! The example is provided for demonstration purposes to explain a specific scenario. No support or maintenance is implied or provided. Further customization is expected to be necessary and it is the responsibility of the end administrator to test and implement an appropriate rule for their specific use case. For access to more tips and tricks, best practices, and ever-evolving creative solutions, we recommend joining us in our active Qlik Community.

Setup:

• Open the Qlik Sense Management Console and open the Security Rules menu
• Click Create new button

ServiceCluster_*,ServerNodeConfiguration_*,Engine*,Proxy*,VirtualProxy*,Repository*,Printing*,Scheduler*,User*,CustomProperty*,Tag_*,License*,TermsAcceptance_*,ReloadTask_*,UserSyncTask_*,SchemaEvent_*,CompositeEvent_*,QmcSection_License*,SystemRule_*

• Press Apply 

Expected outcome:

The user who is assigned to the LicenseAdmin role only has the privilege "License and tokens".

Related Content

• Qlik Sense Management Console sections grayed out and cannot be accessed 
• Security Rules: Control Access to sections in QlikSense Management Console 

Using username and password authentication to a Snowflake target endpoint fails. Testing the connection seems successful, but saving it errors out with:

Incorrect username or password

This is observed in Qlik Replicate 2024.11 SP01 and SP02 with deployments using a custom data directory.

Resolution

This is caused by RECOB-9491, which has been fixed. Review the Release Notes of later releases or contact Qlik Support for access to the early build.

Cause

Use of a custom data directory when installing Qlik Replicate.

Internal Investigation ID(s)

RECOB-9491

Related Content

• Qlik Replicate and Snowflake: Mandated Multifactor Authentication (MFA) starting Q3 2025 

Environment

• Qlik Replicate 2024.11 SP01 and SP02

This Techspert Talks session will address:

• Understanding the schemas
• Demonstration of the migration process
• Best practices and tips for a smooth transition

Chapters:

• 01:05 - How to learn about Qlik Talend Cloud
• 01:52 - Why migrate to Qlik Talend Cloud
• 02:42 - Feature difference highlights
• 03:08 - Using the Migration Inventory Tool
• 06:58 - First look at Qlik Talend Cloud Data Integration
• 07:33 - Creating the first Project and Space
• 08:21 - Creating the Klaviyo Source connection
• 09:54 - Creating the Target connection
• 10:52 - Choosing the task settings
• 12:59 - Viewing Pipeline tasks in action
• 13:55 - Target table differences
• 15:19 - Creating the my SQL source
• 19:24 - Q&A: Will QTC features be added to Stitch?
• 20:04 - Q&A: What is the QTC warehouse architecture?
• 21:45 - Q&A: How to build incremental loads?
• 22:28 - Q&A: Can QTC load data from Marketo?
• 23:37 - Q&A: Why are the schemas different?
• 24:26 - Q&A: Where is the list of data sources?
• 25:23 - Q&A: Where can I get a test account to try it?

Resources:

• About Qlik Talend Cloud subscriptions
• Technical feature comparison
• Performing an inventory analysis
• Qlik Ideation
• Schema Differences in data loading

When using the CICD process, you may point the P2 to patch from your Artifact Repository instead of the Studio update site. Whether using a remote/proxy repository or have uploaded the patch contents to a local repository, you will encounter some error when attempting to deploy, redeploy, or patch your existing P2 deployment.

If you have setup basic authentication for your studio, Eclipse (within Studio) will require the keyring (secure storage) file and master password generated by Studio to gather the authentication credentials for the Artifact Repository and the P2. However, since the defined "secure_storage" file has references to Windows Security, if you attempt to use it on a Linux-based instance for CICD, it will fail due to the missing items. The root reason is the current existing keyring(secure storage) of Talend studio can not be used on another computer. By default, master key is generated by OS related API.

So if basic authentication is required for the P2 to reach out for patch items and there is a Linux-based CICD instance, you can try to re-generate keyring with provided master key in this way the newly generated keyring (secure storage) and master key can be shared to another computer.

Please note even this will not delete your existing secure_storage, though it is recommended to back them up for in case.

How To

1. Create a new secure storage and masterpassword file where the Windows-based Studio instance will be able to access it. Add the same or a new master password inside of your masterpassword file, this will be used on the Linux-based CICD instance later.
2. Generate secure storage file
   • Create a new master key file, for example. C:\Users\xxx\Downloads\mymaster.key and input your secret in the file.

     cat mymaster.key
     mysecretmasterkey
     

   • Update the Studio's .ini file via mapping the keyring and password flags to the newly created masterpassword file. Ensure that any references to the old keypair and password files are commented out. Once validated, save the changes.

     

3. Open Studio, and upon launching to the Project Selection Page, a prompt will appear asking for the credentials. Provide your username and password (or access token), and Studio will save/use those to pull from the Artifact Repository of choice, via the feature manager.

   

4. After choosing the project and it opens up, click the "Feature Manager" to confirm if the supplied credentials are working. If it does, the status window should show the prompt to upgrade to the (specified) patch, or the window to install features/components on the Studio instance. If the window doesn't show up or there is an authentication issue, please consult with your Artifact Repository team and validate the repo location and credentials in the "Windows/Preferences/Talend/Update Settings" area.
5. If successful, navigate to the " Window/Preferences/Eclipse/Security/"Secure Storage" area and uncheck the "Windows Integration (64 bit)" which will disable any Windows specific authentication requirements. Validate that the encryption type is desired for the environment; if different, please choose a specific version. Once confirmed, save the changes via the "Apply and Close" button. This will require a restart of the Studio.
6. The studio should restart and after logging back in, check the new keyring file specified. If there's no mentions to "Windows" reference, then the new keyring creation has been successful, and can be used on a Linux instance.
7. Copy the new files to a location where the P2 can access those files and the files are extracted to a location on the CICD instance where the P2 can access them as well.
8. Add the "-Declipse.keyring" and "-Declipse.password" flags to either the beginning of your Maven_Opts section or the first command that is deploying/updating the P2, and set the values to the files that were copied over. In the example below, the flags point to those files that were copied and extracted in the previous step.

   -Declipse.keyring=/opt/talend-801/keyring/keyring.txt 
   -Declipse.password=/opt/talend-801/keyring/masterpassword.txt

   Additionally, those files can be stored on the scheduler or an external location, and the eclipse flags can point there.
9. Run a build with the new flags, ideally with the

   -Dinstaller.clean=true

   or the specified p2 install directory cleared out.
   • If successful, the P2 should be noted in the build logs of the transfer of files from the repository set, to the P2's defined .installation files. 
   • If the authentication is not successful or the secure_storage files cannot be read by either Studio or the P2, please reach out to Qlik Support for further assistance.

Related Content 

basic-authentication-for-update-repositories-in-studio

Environment

Talend Data Integration 

Qlik Sense encrypts app (.QVF) and data (.QVD) files at time of write to disk. This means that changes to the encryption certificate is not reflected in encrypted files until next time the file is written to disk by the Qlik Sense Engine.  

• QVF file is encrypted when successfully reloaded, either manually or through a reload task. 
• QVD file is encrypted when it is successfully generated through a STORE command in a reload script. 

Completely replacing encryption certificate requires that all encrypted files are re-written to disk with the new certificate. Any file that remains encrypted with old certificate, can only be opened by Qlik Sense Engine if the old certificate still remains in the certificate store. 

If encryption certificate is not available in certificate store, the encrypted QVF or QVD file will not be possible to open by Qlik Sense Engine and any user access to the file will be denied. 

Environment:

Qlik Sense Enterprise on Windows September 2019 and later

Resolution:

A successful key-encryption key (KEK) rotation requires that both the new and old certificate are available in certificate store until key change has been applied on all encrypted files. 

1. Import the new certificate to Windows certificate store on all Qlik Sense Engine nodes
2. Configure Qlik Sense to use the new certificate for encryption
3. Re-write all encrypted QVF an QVD files
   • Save QVF files manually or run reload task 
   • Regenerate QVD files through STORE command in app reload
4. Backup old encryption certificate (in case it is needed later)
5. Remove old encryption certificate from Windows certificate store
6. Validate that all encrypted files can be accessed 

Related Content:

• Data Encryption In Qlik Sense Enterprise On Windows
• Qlik Sense on Windows: Encryption Certificates
• Qlik Sense on Windows: Service Cluster

Qlik NPrinting Designer opens and throws this error message:

Can't find a supported reporting template editor for the file ..... Error Message: Interface not Supported.

The problem occurs only with Office reports. An Office instance is then opened, but not embedded inside the Qlik NPrinting designer.

• The problem occurs even if the zoom in the screen is set to 100% as per requirements
• The problem persists even after a complete un-installation and re-installation of Qlik NPrinting
• The problem can occur on single local machines while Qlik NPrinting Designer works on others

Resolution

To resolve the error:

1. Download and unzip the attached regtlibv12.zip file.
2. Copy regtlibv12.exe to C:\Program Files\Microsoft Office\Root\Office16
3. Open Command Prompt as administrator
4. In the elevated prompt, execute:

   cd  "C:\Program Files\Microsoft Office\Root\Office16"

5. After successfully changing the directory, run the following three commands.

   After each, verify that you receive a confirmation that the registration was successful.

   • regtlibv12.exe EXCEL.EXE

   • Run regtlibv12.exe MSWORD.OLB

   • Run regtlibv12.exe MSPPT.OLB

6. Restart the machine.
7. Verify that NPrinting Designer works.

Upon clicking Edit Report, Qlik NPrinting Designer opens and calls Excel, Word, or PowerPoint to embed the report. 

The communication between the Qlik NPrinting and the Office executables is enabled by type libraries (Typelib) in the Windows Registry (regedit).

By running regtlibv12.exe combined with, for example, EXCEL.EXE, you force Windows to register the type libraries on the registry.

Internal Investigation ID(s)

SUPPORT-584

Environment

• Qlik NPrinting

Qlik Sense uses HTTP,  HTTPS, and WebSockets to transfer information to and from Qlik Sense.

The attached Webscoket Connectivity tester can be used to verify protocol compliance, indicating if a network policy, firewall, or other perimeter device is blocking any of the required connections.

If the tests return as unsuccessful, please engage your network team. 

The QlikSenseWEbsocketConnectivtyTester is not an officially supported application and is provided as is. It is intended to assist in troubleshooting, but further investigation of an unsuccessful test will require your network team's involvement. To run this tool, the Qlik Sense server must have a working internet connection.

Environment:

Qlik Sense Enterprise on Windows 

For Qlik Sense Enterprise on Windows November 2024 and later:

Since the introduction of extended WebSocket CSRF protection, using the WebSocket Connectivity tester on any version later than November 2024 requires a temporary configuration change.

1. Open the Proxy.exe.config stored in C:\Program Files\Qlik\Sense\Proxy\
2. Locate

   <add key="WebSocketCSWSHCheckEnabled" value="true"/> 

3. Change it to

   <add key="WebSocketCSWSHCheckEnabled" value="false"/> 

4. Restart the proxy
5. Run the WebSocket Connectivity tester
6. Revert the change

How to use the Websocket Connectivity Tester

1. Download the attached package or download the package from GitHub: https://github.com/flautrup/QlikSenseWebsocketConnectivityTester
2. Unzip the file
3. Login to the Qlik Sense Management Console
4. Create a Content Library
   
   
   1. Go to Content libraries 
   2. Click and Create New
   3. Name the Content Library: WebSocketTester
   4. Verify and modify the Security Rule
      
      Note that in our example, any user is allowed to access this WebSocketTester.
      
      
      
      
   5. Click Apply
      
      
5. Click Contents in the Associated items menu
6. Click Upload
7. Upload the QlikSenseWebsocketTest.html file.
8. Copy the correct URL from the URL path
   
   
   
   
9. Open a web browser (from any machine from which you wish to test the WebSocket connection).
10. Paste the URL path and prefix the fully qualified domain name and https. 
    
    Example: https://qlikserver3.domain.local/content/WebSocketTester/QlikSenseWebsocketTest.html
    
    

What to do if any of them fail?

Verify that WebSocket is enabled in the network infrastructure, such as firewalls, browsers, reverse proxies, etc.

See the article below under Related Content for additional steps.

Related Content

• Hub access times out with: Error Connection lost. Make sure that Qlik Sense is running properly 

To create a sample document follow below steps. The steps can be applied to all editions of Qlik Sense, such as Qlik Sense Enterprise on Windows and Qlik Sense Business and SaaS.

1. Open Sense (Hub or Desktop) and create a new application
2. Choose Script editor 
   
   

    

3. Press the following key combination: CTRL 0 0
4. This generates an automatic script with random data:
   
   

    

   Content:
   
   

   Characters:
   Load Chr(RecNo()+Ord('A')-1) as Alpha, RecNo() as Num autogenerate 26;
    
   ASCII:
   Load 
    if(RecNo()>=65 and RecNo()<=90,RecNo()-64) as Num,
    Chr(RecNo()) as AsciiAlpha, 
    RecNo() as AsciiNum
   autogenerate 255
    Where (RecNo()>=32 and RecNo()<=126) or RecNo()>=160 ;
    
   Transactions:
   Load
    TransLineID, 
    TransID,
    mod(TransID,26)+1 as Num,
    Pick(Ceil(3*Rand1),'A','B','C') as Dim1,
    Pick(Ceil(6*Rand1),'a','b','c','d','e','f') as Dim2,
    Pick(Ceil(3*Rand()),'X','Y','Z') as Dim3,
    Round(1000*Rand()*Rand()*Rand1) as Expression1,
    Round(  10*Rand()*Rand()*Rand1) as Expression2,
    Round(Rand()*Rand1,0.00001) as Expression3;
   Load 
    Rand() as Rand1,
    IterNo() as TransLineID,
    RecNo() as TransID
   Autogenerate 1000
    While Rand()<=0.5 or IterNo()=1;
   
    Comment Field Dim1 With "This is a field comment";​

5. Click Load Data 
6. This loads in a very simple data model that can be used to test the basic functionality of Qlik Sense.

 

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.

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
• If the cursor token is returned in the response header instead of the response body, the 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. 

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

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.
      

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.

NPrinting has a library of APIs that can be used to customize many native NPrinting functions outside the NPrinting Web Console.

Environment:

Qlik NPrinting 

An example of two of the more common capabilities available via NPrinting APIs are as follows

• Connection reloads
• Publish Task executions

These and many other public NPrinting APIs can be found here: Qlik NPrinting API

In the Qlik Sense data load editor of your Qlik Sense app, two REST connections are required (These two REST Connectors must also be configured in the QlikView Desktop application>load where the API's are used. See Nprinting Rest API Connection through QlikView desktop)

• GET
• POST

Requirements of REST user account:

• Windows Authentication is required in both these connectors. The required user account is the NPrinting service account (which is also ROOTADMIN on the Qlik Sense server)
• This user account must also be a member of the NPrinting 'Administrators' Security Role on the NPrinting Server.

Creating REST "GET" connections

Note: Replace QlikServer3.domain.local with the name and port of your NPrinting Server

NOTE: replace domain\administrator with the domain and user name of your NPrinting service user account

Creating REST "POST" connections

Note: Replace QlikServer3.domain.local with the name and port of your NPrinting Server

NOTE: replace domain\administrator with the domain and user name of your NPrinting service user account

Ensure to enter the 'Name' Origin and 'Value' of the Qlik Sense (or QlikView) server address in your POST REST connection only.

Replace https://qlikserver1.domain.local with your Qlik sense (or QlikView) server address.

Ensure that the 'Origin' Qlik Sense or QlikView server is added as a 'Trusted Origin' on the NPrinting Server computer

Related Content

• Distribute NPrinting reports after reloading a Qlik App
• Extending Qlik NPrinting
• Run a Qlik NPrinting API POST command via QlikView reload script
• Troubleshooting Common NPrinting API Errors

NOTE: The information in this article is provided as-is and to be used at own discretion. NPrinting API usage requires developer expertise and usage therein is significant customization outside the turnkey NPrinting Web Console functionality. Depending on tool(s) used, customization(s), and/or other factors ongoing, support on the solution below may not be provided by Qlik Support.

Account Types 

• Personal Account:

Once the connector has authorization to access the Microsoft account there will be a corresponding entry in "My apps"
https://myapps.microsoft.com/

• Enterprise Account:

Granting Access for Enterprise Accounts:

Once the enterprise application is selected an application list will appear that the user can filter searching for Qlik Web Connector:

Enabled for users to sign-in? (Yes)

User assignment required? (Yes) This field is only mandatory if the administrator wants to restrict access to the users.

Visible to users? (Yes)
 
 

Testing (With administrator rights)

Open Qlik Office 365 SharePoint connector and select "Can Authenticate" and the press the green button "Authenticate"


You will be redirected to a Microsoft login page that should look similar to the following picture:
 

If azure grants access, the Qlik Webconnector application will generate a code as the following one:



Testing (With NON administrator rights)

If a basic (Non admin) user tries to auth the following message would appear in azure:

In order to fix this the administrator needs to grant access to the users.


Once the administrator granted access to the user the message that should appear is the following one:

Document thumbnails on the QlikView AccessPoint are either missing/blank or showing No Preview Available.

The thumbnails on the QlikView AccessPoint are not refreshing after being updated. 

Environment:

• QlikView Server, all versions

This issue can have multiple root causes. 

Saved in WebView mode

The QlikView document may have been saved in WebView mode. In this case, the .qvw will not display a thumbnail on the AccessPoint and always show No Preview Available. 

To solve: Ensure "Web View" is not active in the document and resave it. 

To turn off WebView go to View in the toolbar and toggle Turn on/off WebView

The wrong sheet is selected for thumbnail creation

Verify that the correct sheet is used for creating the thumbnail.

To solve: Open the document and verify the setting.

To do so, go to:

• Settings
• Document Properties
• Opening tab
• Ensure Document Thumbnail is set to "Opening Sheet"

QlikView Server cached the wrong data

QlikView may have the wrong data for the thumbnail cached. 

To solve: Restart the QlikView Server service. This will clear the cached data or configure how frequently the thumbnail cache is being updated. 

PLEASE NOTE: The refresh interval only applies to a situation where the Thumbnail should be updated following a reload in the desktop client in graphical mode. Reloads done via the QlikView Distribution Service or via batch will not update the thumbnail. This is a known limitation.

To change the setting:

1. Stop the QlikView Server Service
2. Edit the settin.ini file located in “C:\ProgramData\QlikTech\QlikViewServer” 
3. Add “QvThumbnailCacheUpdateInterval=X” inside the [Settings 7] section of the file, where X equals the custom number in minutes

Example:

[Settings 7]
   QvThumbnailCacheUpdateInterval=2

   NOTE: The setting.ini must have an empty line at the end, in order for settings to apply.

4. Save the file and start the QlikView Server Service
5. Restart the QlikView WebServer service, or if using IIS, perform an IISRESET from a CMD prompt

Manually force a refresh of the Thumbnail

If the above fail, try toggling the setting under QlikView Desktop > Settings > Document Properties > Opening > Document Thumbnail, to "None". Then reload the app, and change the setting back to "Opening sheet", and reload the app. 

Cause:

This situation may occur if there were changes to the thumbnail configuration in specific documents prior to being published. Configuration is under QlikView Desktop > Settings > Document Properties > Opening > Document Thumbnail.
QlikView Server may still be in the process of caching some thumbnails information or has not yet reached the thumbnails caching system routine which may have been interrupted by external factors.

The following error is shown next to Connection in Database Configuration page of Talend  Administration Center when using MySQL DB.

Cannot connect to database (null, message from server: "Host xxxx is blocked because of many connection errors: unblock with 'mysqladmin flush-hosts'") 

Resolution

1. Please check your environment if the reasons mentioned in the "Cause" section are affecting you to have many connections.
2. Unblock using "mysqladmin flush-hosts" as mentioned in the error.
3. There 2 things need to be done on the MySQL DB end with the help of your DBA for now.
   • Run the flush host command.
   • If there is a maximum connection until error value that you can set (For example: max_connect_errors in MySQL), please Increase the max number of connections on the DB end (set it to a higher value to handle more connections).
   • Please check the above, do the changes on the DB end, clear the cache on the Talend Administration Center end and do a restart of Talend Administration Center Application, this would help you to fix the issue.

Cause

This issue could be caused by two main factors in general

NetWork Connection

1. Network connectivity issues between Talend Administration Center Application server and the MySQL database server.
2. Firewall or security group settings blocks the connection.
3. Health check or port scan in other systems may be connecting to the server.>

MySQL DB

1. The MySQL server is down or not accepting connections.
2. Incorrect database connection configuration in Talend Administration Center Application.
3. The database server has reached its maximum connection limit.

Related Content 

How-to-clear-the-Talend-Administration-Center--cache

Environment

Talend Administration Center 

Step by Step Instructions 

Links provided in these examples are example links, not real links. 

1. Using a supported web browser, open up the Qlik Web Connectors Console
   YourWebConnectorServer:5555/web
2. Locate and click the Qlik Office 365 Sharepoint Connector
3. Select the CanAuthenticate table in the available Tables list on the left.
4. Click Parameters
5. Copy your Sharepoint base URL (where the file is located) into the Base URL field
   https://<yourO365TenantID>.sharepoint.com
6. Click Authenticate
7. This will open a new browser window with your Authentication Code. Copy the code to clipboard. 
8. Return to the previous browser window and paste the code into the Authentication Code field. Click Save.
9. Now click Save Inputs & Run Table
   A confirmation will be shown in the Data Preview tab reading true in the authenticated row.
10. Locate the lists table in the Available Tables list on the left.
11. Click Parameters 
12.  Provide the Base URL and Sub Site Path
    
    • Base URL: https://<yourO365TenantID>.sharepoint.com
    • Optional include sub site Path: /sites/<yoursubsiteDirectoryPath>
13. Click Save Inputs and Run Table
14. The Connector will now attempt to preview the data
15. Click the Qlik Sense (Standard Mode) tab
16. Copy the URL provided:
    http://localhost:5555/data?connectorID=Office365Connector&table=Lists&subSite=sites%2fstt&appID=
17. Go to your app in Qlik Sense

18. And 'Create new connection' -> 'Web file', using URL: 'http://localhost:5555/' and give it a name.

19. Create a connection variable: let vQwcConnectionName = 'lib://Connection_name';

Environment

• Qlik Web Connectors

Related Content

How to load a file from SharePoint 365 using Qlik Using Qlik Web Connectors on premise 

Qlik Sense fails to export a sheet to PDF and returns a blank page. 

When exporting an object as an image, the error:

An error occurred during export. Please try again.

Environment:

Qlik Sense Enterprise on Windows 

Resolution:

1. Verify if port 4899 is available. Unblock if it is not. 
2. Check the System_Printing log to see if the following error message can be found:
   
   Failed to connect to an IPC Port: The system cannot find the file specified. Server stack trace: at System.Runtime.Remoting.Channels.Ipc.IpcPort.Connect(String portName, 
   
   If so, please continue the following:
   1. Go to  C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\
   2. Make a backup of machine.config file first
   3. Open machine.config to see if the following line is included:
      

      <commonBehaviors><endpointBehaviors><Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior/></endpointBehaviors><serviceBehaviors><Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior/></serviceBehaviors></commonBehaviors></system.serviceModel>​

   4. Delete this line and save the file
   5. Restart QlikSense printing service

Qlik provides a QlikView Converter tool to convert QlikView documents (QVW files) to Qlik Sense apps. The converter tool can be used in the Dev Hub in Qlik Sense Enterprise and Qlik Sense Desktop.

Using the tool on the Qlik Sense Dev Hub may successfully proceed by converting Dimensions, Measures, Visualizations, and Variables, but will then fail as soon as the Create app button is clicked:

Internal Server Error

The following error is shown in the QlikView converter tool:

Global ERROR UserId: User.Name4Server.com@USERDIR, Error: More than one user matching UserDirectory=USERDIRECTORY; UserId=User.Namel%Server.com

Resolution

The QlikView converter tool is provided as it is.

It is possible that some specific server configurations are not fully compatible with this tool. In some cases, user directories are not read correctly and may require the encoding system to be changed from ascii to utf8. 

If this does not work, it is possible to use the same functionality provided by Qlik Sense Desktop.

Change the encoding system:

1. Find the QSBuild.js file located in C:\Program Files\Qlik\Sense\ConverterService\node_modules\@qlik-trial\freyja-qsbuild\dist\src
2. Open the file in, for example, Notepad++
3. Set QSBuild.js to read UTF8 for AD accounts.
   
   To do so, modify the following string from: 
   

   const base64EncodedHost = FileSystem.readFileSync("C:\\ProgramData\\Qlik\\Sense\\Host.cfg", "ascii");

   to
   

   const base64EncodedHost = FileSystem.readFileSync("C:\\ProgramData\\Qlik\\Sense\\Host.cfg", "utf8");

Use Qlik Sense Desktop

1. Install Qlik Sense Desktop on a local machine
2. Work with the QlikView converter tool provided by Qlik Sense Desktop

Environment

• Qlik Sense Enterprise on Windows (Dev Hub)
• QlikView Converter

Azure Synapse as the target may be affected by a defect that causes the endpoint to not correctly path the staging folder. Extra slashes (/) may be observed in file paths, leading to files not being loaded to the target correctly when Azure SQL copy commands are executed.

No errors are logged or displayed and the staging files remain available in the correct folder. The only symptom of this issue is data not being replicated to the base tables.

Resolution

Affected Versions

Qlik Replicate November 2024 SR1 (current) and all earlier versions.

Fix Version

A patch will be released in the future to address this issue. Early build 2024.11.444 is being actively developed and can be requested using a Support case. 

Workaround

To mitigate the issue, use ADLS Gen2 storage instead of BLOB storage. SUPPORT-1644 only impacts BLOB storage.

Cause

This is caused by SUPPORT-1644, which leads to incorrect file paths between the staging folder locations and the copy commands executed by the task. Qlik is actively working on resolving the issue. 

Internal Investigation ID(s)

SUPPORT-1644

Environment

• Qik Replicate

Connecting to a Windows hosted Qlik Replicate Server using repctl connect fails with the following error:

[connect command] Failed
Failed to connect to replicate server. Server: localhost, port: 3550 (exit status 1000302)
Receive buffer too small. Required size=4, Plaintext size=1093808600 (exit status 1003615)
Failed to receive: An established connection was aborted by the software in your host machine.
(10053) (exit status 1003513)

Resolution

Define the correct path in the repctl connect command:

1. Open a command line with elevated permissions (As Administrator). 
2. Specify the full path using the "-d" switch immediately following "repct.exe", then complete the command with the remaining parameters.
   
   Example:
   

   repctl.exe -d "YOUR_DATA_DIRECTORY_PATH" connect

Cause

Qlik Replicate may be set up in HA mode (configured with a shared folder) or have a custom data folder. 

See How to move the Data Directory to a different Qlik Replicate Server.

Environment

• Qik Replicate

The following error message is from Talend Remote Engine Karaf Log.

pairing service error response received with status 404 - No Engine was found with Pre-authorized key ****

Resolution

1. Please install a fresh new Talend Remote Engine from the Talend Management Console or the marketplace (Azure or AWS), and set a new pairing key for the installation.
   • Stop Talend Remote Engine Server.
   • Make sure remote.engine.id = is blank in etc/org.talend.ipaas.rt.pairing.agent.cfg file
   • Get the new key from TMC and update preauthorized.key.cfg file with new key.
   • Remove everything under <remote-engine>/data folder and clean key in org.talend.ipaas.rt.pairing.agent.cfg file

     rm -r cache/

   • Start the  Remote Engine Server
2. If the issue does not get fixed even did a fresh installation, please try the newest version of the Talend Remote Engine to see if it can fix the problem.
3. If the issue persists, please contact our technical support team as a customer or partner of Qlik for further investigation.

Cause 

It seems it was not paired corrcetly and then connection between RE and TMC is not taking place.

Potential Points

1. The key that you set during the installation of the Talend Remote Engine is incorrect.
2. The key that you have set before is being used.
3. An issue may have occurred during the installation process of the Talend Remote Engine.

Related Content 

creating-and-pairing-remote-engine-programmatically

Environment

Talend Cloud