Hi,

Apologies for the slightly vague question but is there anything changed in the last few weeks that will have broken some old visualisation extensions - specifically in cloud - on prem and even technical preview QS desktop seem fine?

more detail:

probably 7 or 8 years ago I hacked together my first extension following the very few tutorials available and it worked reasonably well - i'm no web developer but got it working and seemed performative if almost certainly no where near any best practice standards or anything.  Has had a few tweaks to the internal logic over the years but in terms of structure its not really changed, to my great surprise it even worked when copied to the cloud.  As far as i'm aware they were still working a few weeks ago but as of yesterday (possibly earlier) the don't render, nothing is jumping out to me in the console log other than this (there are a bunch of launchdarkly errors but they are there extension or no and more of a whitelisting thing from what i read)

which doesnt appear in the QS desktop (Nov 26 technical preview) dev tools so am wondering if its being enforced maybe?

If anyone has any ideas or if i've missed something, would greatly appreciate it

Hi, I have a question concerning the way Outer SetAnalysis modifiers are working. 

In my below example, I use an application that contains data for Years 2022 and 2023. There is no data for 2021. 

I have a standard calculation that counts the number of Customers that is:

count(distinct Customer_ID) = 1500 

If I use SetAnalysis on the field Year only, it will work as expected, using an inner Set Analysis or an outer Set Analysis:

• Inner: count({<Year={2022}>}distinct Customer_ID) = 1000
• Outer: {<Year={2022}>}count(distinct Customer_ID) = 1000

If I do the same but put 2021 instead of 2022, since I don't have data for 2021, the expected result should be 0, which is the case, for both Inner and Outer Set Analysis.

However, as soon as I introduce another set modifier in my inner set analysis, and I put year 2021 in my Outer Set Analysis, the behaviour gets weird:

• Only Customer_Segment: count({<Customer_Segment={'Employer'}>}distinct Customer_ID) = 750 - OK
• All Inner: count({<Year={2021},Customer_Segment={'Employer'}>}distinct Customer_ID) = 0 - OK
• All Outer: {<Year={2021},Customer_Segment={'Employer'}>}count(distinct Customer_ID) = 0 - OK
• Year in Outer, CustSeg in Inner: {<Year={2021}>}count({<Customer_Segment={'Employer'}>}distinct Customer_ID) = 750 - NotOK. 750 is the total number of customers for the Customer_Segment 'Employer'

It seems like, when there is an inner set analysis, and we apply an outer set analysis with a modifier that is not in the data set (Year = 2021 in this example), this outer set analysis modifier is simply ignored, instead of resulting in 0. 

After doing some more tests, if we have 2 modifiers in Outer SA (1 out of dataset, 1 within data set), and 1 or more modifiers in Inner SA, the modifiers from Outer SA that is out of dataset will be ignored (like above), but the second modifier will still be considered.

Is this the expected behaviour for Outer set analysis? Should it be the exact same result as when we use same modifier in Inner Set analysis? 

I confirm that I don't use and Set Identifier ($, 1, ...)

Thank you in advance for your help

Hello, IA is being tested by most of our customers. As everybody knows all SaaS products come with a number of free Qlik Answers questions: 25 for Starter, 200 for SaaS user based or Standard and 1.000 for Premium and Enterprise. This year Qlik changed the rule for overage. Only Capacity has overage enabled. All other features come with overage disabled, including Answers.

We came across several customer using beyound their contracted limits. So we have two questions: 1 - Who and how can we flag the tenant to disable Answers overage, 2 - Are we going to receive invoices for these overages?

Thank you 

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’m trying to use Qlik Cloud Data Integration with a Replication project.

I have:
- Qlik Cloud license with 25 GB capacity
- Talend license valid for 1 year
- all available admin permissions assigned to my user
- a verified Microsoft Dynamics 365 Business Central connection

The problem is that in the Replication project, under Create new, I only see Connection.

I do not see the Replicate data option shown in Qlik documentation/videos:

https://learning.qlik.com/student/activity/2560656-how-to-create-a-replication-task?from_embedded_video=true

Is this option dependent on a specific Qlik Talend Cloud license or entitlement?

Hello Community,

I’m backing up Qlik apps without data to GitHub and restoring them through Qlik Cloud Automation.

The Base64 Legacy Block flow works for small files (under 1 MB), but:

• When used Native Export App Block returns a file object; and GitHub’s commit block requires Base64 Content.
• Get Repository Content Github Block returns no inline content above 1 MB.
• Call URL → native Import App, mapped body into File, it returns HTTP 200 but fails with error showing "file": null and missing file/file_resource.

The same Call URL method performed through Postman, QVF downloaded and imports manually successfully.

How can I pass a GitHub download into native Import App, and commit native Export App output without legacy Base64 blocks? 

A working example would help.

I have uploaded a Restore Qlik Cloud Automation for the reference. 

Thanks

See e.g. https://www.heise.de/en/news/eMudhra-incident-compromises-eight-CA-certificates-11494689.html

Qlik Sense seems to use node.js and go. Thus, I expect qlik needs to be patched, right?

Please let us know which patches are necessary and their ETA if not yet released.