Did someone check out that Qlik Sense sheet? I can't see it anymore!

Did you hear your colleague ask that question into the shared office / on Teams / Slack ? Then I have a perfect extension for you: Hello data+

On Qlik Cloud, editing a published sheet means making it private first. From that moment on, nobody else can see it, and you had better not get distracted and forget to publish it again. If the app is published to its managed space while the sheet is still "checked out", the managed version loses that sheet too.

Hello data+ closes that gap for developers working on updates of published sheets:

• Tag each sheet as intended to be public or private
• Get reminded when a sheet meant to be public is still private, or the other way round
• Clone a sheet for editing, while the original stays public the whole time
• Sync every kind of change back to the original sheet's objects
• Republish the managed app with one click, right from within the app

The smallest unit of change is now a single object, not the whole sheet, and you work on a specially tagged copy. Take all the time you need, and deliver your updates in parts if you like.

A version for client-managed will be available in December too.

Motivation

With the Data+ Suite, we care about much more than just write-back scenarios. Those familiar with my GitHub projects, Quick Table Viewer and Guided Tour Extension, will be pleased to know that LeitArt has included both in the supported package at no additional cost. And Hello data+is the next extension you don't want to miss!

Join the early-access

Register at https://waitlist.leitart.de and be among the first beta testers in November 2026.

Hello
I got a master visualization which is a combo chart with 3-bars expressions (stacked) and a line expressions
the combo chart looks something like this:

Now what I want is to break this chart by the top 8 accounts but the trellis is repeating the chart for all 8 accounts

I put advanced mode and added to the expressions the $(vDimSet) and in the dimension I put the following dimension:
=Aggr(
If(
 Rank(Sum({<[Portfolio Level 2 ID]={87}, SCENARIO_TYPE, SCNR_TYPE_ID={0}>} AMOUNT * MANDAYS_SPENT * FLG_MANDAYS_SPENT_INCL_DU), 4) <= 8,
ACCOUNT_DESCRIPTION
),
ACCOUNT_DESCRIPTION
)

but all in vain
I also put the ACCOUNT_DESCRIPTION as the dimension in the trellis and moved the logic of the ranking to the expressions but trellis displays blanks or diplays 1 bar expression and repeating it as above
i tried to put 8 distinct charts but the performance is extremely slow
kindly advise

Hi everyone,

We are experiencing an OAuth 2.0 authentication issue when trying to connect Qlik Cloud Analytics to Salesforce using the Salesforce connector from Add Data.

A new Salesforce External Client App was created following Salesforce's recent security changes.

According to Salesforce's updated security requirements, PKCE is mandatory for newly created applications, and the option to disable it is locked.

However, the Qlik documentation instructs us to disable PKCE as part of the connection setup.

We attempted to configure the Salesforce Callback URL using both:

https://connector.qlik.com/auth/oauth/v2.htm

https://connector.qlik.com/auth/oauth/v3.htm

Both attempts failed during authentication, resulting in the following errors:

redirect_uri_mismatch

OAUTH_APPROVAL_ERROR_GENERIC

We would appreciate hearing from anyone who has encountered a similar issue or has successfully established a Salesforce OAuth 2.0 connection in Qlik Cloud Analytics under the new PKCE requirements.

Thanks in advance for sharing your experience!

Our infrastructure security scanner flagged our Qlik Sense servers as potentially vulnerable because of the bundled Node.js 24.18.1 runtime. Following the October 21, 2026 Node.js security release, I tested updating that binary independently of a Qlik patch.

A scanner finding against a runtime version does not establish that the vulnerabilities are exploitable through Qlik Sense. Product-specific impact still needs confirmation from Qlik.

The update from Node.js 24.18.1 to 24.22.1 passed testing in our Qlik Sense Enterprise on Windows May 2026 Patch 7 environment. This is one environment's test result, not a compatibility guarantee.

This experimental method is not validated by Qlik. Qlik's documented approach is to update the bundled runtime through a Qlik Sense upgrade. This post shares a technical test, not an official remediation recommendation. If evaluating it, use development first, a maintenance window and a recoverable full backup.

Check the bundled version

& "$env:ProgramFiles\Qlik\Sense\ServiceDispatcher\Node\node.exe" --version

The full path checks Qlik's runtime rather than another Node.js installation on the PATH.

Run the attached scripts

1. Extract the scripts into one folder.
2. Download the official Node.js 24.22.1 Windows x64 binary.
3. Edit NodeUpdate.config.psd1: configure the binary, backup and log paths, and set the expected SHA256 using the win-x64/node.exe entry in SHASUMS256.txt.
4. Open Windows PowerShell 5.1 as administrator and run the backup:

.\01_Backup_Node.ps1

Continue only after BACKUP VERIFIED:

.\02_Update_Node.ps1

Leave the Service Dispatcher running before starting the update: the script handles stopping and restarting it. Execution is local to each machine; relative paths are resolved against the configuration folder.

Validate and roll back

Check Hub, QMC, application access, exports, reloads, usual connectors and Qlik logs. These are suggested checks, not a claim that all were covered in our test.

To roll back, set RestoreBackupDirectory to the exact original backup folder, then run:

.\03_Restore_Node.ps1

The scripts target the main Service Dispatcher runtime on Node.js 24 only. They do not update EAPowerTools, Package Cache or npm dependencies. A binary backup is not a full site backup, and automatic rollback is not guaranteed. Recheck the installed version after subsequent Qlik maintenance.

Sources: Node.js security bulletin, October 21, 2026; Node.js 24.22.1 release notes, October 21, 2026; Qlik Support guidance, updated August 14, 2024.

Hi,

I have a task that will be insert only and has a high volume of changes. I read that "Optimize Inserts" in the Change Processing Tuning settings can increase performance. However, the documentation also says that this setting can result in duplicates as shown below:

Is this only relevant when "Apply changes using SQL Merge" is enabled alongside "Optimize Inserts"? Because we will not have "SQL Merge" enabled. Our target will be Snowflake.

Help with this is appreciated. Thank you.

Regards,

Mohammed

現在、Talend Studioを使用する中、Basic認証からOauth認証へ切り替えをしようとしています。

Studio内のメタデータよりTest Connectionをしているもののエラーの状態です。

どこに不備があるのか教えていただきたいです。

添付のとおり、Talend8を使用し、HTTP500エラーが生じます。他の項目については問題ないはずで、別のプログラムから接続処理をしたとき本パラメーターでJWTのトークン取得でき、Salesforce側にログイン履歴が正常にでています。

Hi Support,

I have setup a data replication task in Qlik Cloud Data Integration, and I'm looking to use one of the provided expression headers to add a column to a table. However, when I use the header in the expression, I get a validation error with the following message: "The column expression is not valid: test. The attribute Q_H_OPERATION does not exist in the source dataset."

My understanding is that the column wouldn't need to exist in the source dataset since it's meant to provide metadata of the source table rather than data of the table. This wasn't an issue when using expression headers in Qlik Replicate for the same purpose.

The replication task has a SQL Server source and SQL Server target. The data movement gateway is version 2026.5.37.

Please let me know if you need any further information. Any insight into the issue is greatly appreciated.

Thanks,
Nak

Hi team,

Need one suggestion in qliksense +(nprinting)

We have dynamic view chart in qliksense dashboard but as we know that nprinting is not supporting dynamic views..

What can be work around to extract dynamic view chart in pdf

I tried

1: creating a story then export
2: sheet export as pdf
3: extension+ mash-up

No success with option 1 & 2
With option 3 I achieve it, but not good and dynamic solution for all dashboard who have dynamic view charts.

Thanks in advance!

Regards,

Prashant

Is there a way in Talend Cloud to upgrade a jar file version for Talend jobs without re-doing the "Publish to Cloud" from the Studio?
FYI, the current approach is 
    1. In Studio Modules, upgrade the jar file to higher version. e.g. log4j 2.17.1 to 2.25.4
    2. "Publish to Cloud" for all active production jobs
    3. Promote all jobs to production
When there have dozens or hundreds active production jobs, there should be a better way than re-promoting all jobs to production (release) due to upgrading a single jar file version.