We are using the Qlik Sense application in our organization, and before moving it to production, we need to obtain approvals from the load testing team. As part of this process, we are attempting to record the application using JMeter.

However, while trying to record the script, we encounter the following error:

"Connection Lost. Make sure that Qlik Sense is running properly. If your session has timed out due to inactivity, refresh to continue working."

Due to this, we are unable to proceed with the script recording. Interestingly, the application works perfectly fine when accessed normally outside of JMeter.

Has anyone faced a similar issue or can guide us on how to resolve this?

Hello, does anybody know what new types of visuals are coming in Qlik Sense, if any? Maybe someone read somewhere, or Qlik staff can tell, or anything else. I am looking for some specific solutions and just need to decide whether to wait for a native implementation or not. Thanks.

Hello,

We have 2 QlikView Desktop under license.

We would like to evaluate QlikSense. 

Any possibility to download a trial version or activate a license for limited period of time?

Thanks in advance for your support,

Thierry Meessen

Hi !
I'm trying to import data from a Qlik Sense app using a REST API connector, and when creating the REST connector, I get "HTTP protocol error 500 (Internal Server Error): {"error":"Internal Server Error: null","status":500}".

The JSON format to be imported is like this:
[
  {"id":"1",
   "modulo":"ERP",
   "version":"6.1"
  },
   {"id":"2",
    "modulo":"CRM",
    "version":"8.2"
   }
]

The strange thing is that when importing from another version of the same API, which returns a compact JSON format (without spaces or line breaks between fields), it works perfectly, both when creating the REST connector and via script.
The format that works well is this:
[{"id":"1", "modulo":"ERP", "version":"6.1"},
{"id":"2", "modulo":"CRM", "version":"8.2"}]

Both endpoints are visible from Qlik, don't require pagination, and have the correct authentication and parameters. Both JSONs has no hierarchical structure, and the result output is about 400 records.

I'm using client managed Qlik Sense Enterprise February 2023 Patch 2, qliksenseserver: 14.113.4

This script works well with the compact JSON API, but does not work with the JSON API with breaks and spaces.

LIB CONNECT TO 'Rest_Api';

RestConnectorMasterTable:
SQL SELECT
   "id",
   "module",
   "version"
FROM JSON (wrap on) "root"
WITH CONNECTION
( Url "https://xxx.xxx.com/api/reports/modulos?FechaDesde=2024-01-01&ACCESS_TOKEN=xxxxxxxxxxxxxxxxxxxxx");

Report:
LOAD
   id,
   module,
   version
RESIDENT RestConnectorMasterTable;

DROP TABLE RestConnectorMasterTable;

Does anyone know how to remove spaces and line breaks from JSON preferably from Qlik Sense ? I need to access many APIs, and modifying them all isn't the best option.

Thanks in advance.

Regards,
Fernando

I have a report with the Date Range Picker. I am able to see the object in my work stream and in the public stream. When any other user opens the report they see an error message instead of the data range picker. 

What I see

What everyone else can see

Hola a todos, estoy utilizando Qlik Cloud y quiero poder visualizar información al pasar el mouse por los datos, es decir, si en una columna se calcula una suma, quiero que al pasar el mouse por cada dato en la columna pueda detallar la información que lo conforma, ya sea manual o formulado.

Our client has requested to change security on data to include multiple levels - which corresponds to the fields in Product Dimension.

Product Dimension has multiple fields, including ID1,ID2,ID3. Our current security is on ID1 only. The request is to change it so different combinations of access based on these 3 columns can be done. For instance:

1. client A should have access to ID1 = 100 and all ID values within ID2 and ID3
2. client B should have access to ID1 = 100 and ID2 = 200 and all ID3 values
3. client C should have access to ID1 = 100 and ID2 = 200 and ID3 = 300

I have created section access table that looks like below and tried testing ClientC access, but getting Access Denied message. Is there a limitation in Qlik that section access cannot be created on multiple fields w/n the same dimension (except only when those multiple fields are concatenated into 1 field)

In our process, we only get ID (or IDS) to be used for security. For instance, Client A was provided with ID1 = 100, which implied that all values available under ID2 and ID3 need to be accessible.

These IDs (especially ID2 and ID3) are not static and new IDs can be added at any time. How do I account for such setup to ensure that access is granted on different combinations of these IDs?

Target Data System: Snowflake

GitHub : Project connected

Source Data System: QDI Project (Cross Project Pipeline)

• Source project is connected to a MS SQL server

Qlik Cloud 

Scenario: The Metadata project level settings affecting suffixes and prefixes for a Data Integration project are not being reflected into the push-down SQL. They in fact seem to be overwritten by Qlik Cloud and cannot be edited. We have only noticed this scenario when connecting projects to GitHub. This was not an issue prior to this week (3/31-4/4).

Details:

We are attempting to create a Data Integration project that we have versioned in GitHub by utilizing the steps mentioned in your help docs to "Share a project with another Space or Tenant" https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/DataIntegration/VersionControl/Project-version-control.htm

When following  these steps and pulling down the changes from our main branch we then create a new branch to facilitate development for this project. Once the new branch is created, we then validate the "Metadata" project level settings to see that the suffix and prefix values are all set to a lowercase convention. We then prepare the first task in the pipeline and get the following error:

Prepare data task failed: Jobs execution failed. Job finished with error for process: "Create or replace transformation view 'HISTORY', for dataset 'AVT'". Failed to execute sql: Create or replace transformation view 'HISTORY', for dataset 'AVT'. SQL compilation error: Object '<Database>.<Schema>.AVT__HISTORY' does not exist or not authorized.

In the error above we can see that the suffix for the AVT history table is uppercase and not lowercase like specified at the project settings. However, when viewing the project settings again we can see that the lowercase convention has been overwritten to uppercase:

When checking the SQL Preview for this dataset we can also see that the query being executed  has the same uppercase convention. Furthermore, in the Snowflake query history for the warehouse we can see the exact same SQL being executed:

When attempting to change the "Metadata" project level settings we can see that the "OK" confirmation button is grayed out and prevents the setting from being updated.

We also checked the source Storage Task dataset leading into this project (cross project pipeline) and the settings were also set to lowercase and when returning to the project they are defaulted to uppercase. The table was however, created with the lower-case suffix in Snowflake.

In summary, there seems to be an inconsistency on how Qlik Data Integration applies these settings when building the pushdown sql for executing data tasks. This is a complete show stopper for Snowflake based pipelines since Quoted Identifiers are used extensively in all Data Integration pushdown SQL for this target data system to which, the case of table names and other objects are incredibly important.

On the "General" TAB, both counts are 0 licenses (of X number) of NAMED CALs     and   0 licenses (of Y number) of DOCUMENT CALs.    How do I get those counts correctly reset ??    We tried starting the individual QV services on the server... and then tried a server RESTART. 

Now, after the RESTART, the count of the NAMED CALs is slowly rising; appears to be when someone (who USED to have a NAMED CAL) logs in, the system keeps track on that user.  The DOCUMENT CAL number is NOT increasing now, however...