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

This Techspert Talks session covers:

• Talend Migration approach
• Qlik Talend Cloud Migration Toolkit
• Migration demo

Chapters:

1. 01:12 - Migration Paths and phases
2. 02:31 - Overview of Toolkit
3. 03:52 - Updates to the Toolkit
4. 05:08 - Where to download
5. 06:11 - Migration Toolkit Demo
6. 07:29 – Inventory
7. 09:46 – Assessment
8. 12:00 - Runtime Usage tool
9. 13:32 - Unlocking Migration
10. 14:29 - Migrating Administrative Assets
11. 15:39 - Migrating Talend Projects
12. 16:42 - Phase 0: all the pre-built fixes
13. 18:40 - Creating the Migration Manifest
14. 21:42 - Migrating Runtime Assets
15. 23:14 - Reviewing a production migration
16. 25:17 - Q&A: Will Talend On-Prem still be supported?
17. 26:02 - Q&A: Can Profession Services help?
18. 26:32 - Q&A: Should we upgrade JDK first?
19. 27:10 - Q&A: How to monitor usage on the Cloud?
20. 27:28 - Q&A: Is there High Availability on Talend Cloud?
21. 27:55 - Q&A: How does Talend define 'last cloud version´?
22. 28:34 - Q&A: Can it migrate Replicate or Stitch?
23. 29:13 - Q&A: How to assess the quality of our code?

Resources:

• Installing Qlik Talend Cloud Migration Toolkit
• Talend Project Quality

Click here to see the video transcript

Hello team,

I am writing to inquire about the limitation on using Filters in bidirectional replication tasks.

According to the user guide below, it states that Filters should not be used in bidirectional replication:
https://help.qlik.com/en-US/replicate/May2026/Content/Global_Common/Content/SharedEMReplicate/Design%20Tasks/Limitations_bidirectional_tasks.htm#ar_tasks_1150461142_1273508

Our customer has specific records within the target tables that they do not want to synchronize (for example, keeping records with IDs 1 to 10 isolated within their respective databases only).
Therefore, they would like to apply a Filter.
Theoretically, it seems possible to achieve this by configuring symmetrical filters on both tasks in the bidirectional setup.
Could you please clarify the specific technical reason why using Filters is restricted/not recommended in bidirectional replication?

Additionally, if using Filters is strictly unsupported or carries technical risks (such as infinite looping or data divergence), could you advise on any recommended workarounds to achieve this requirement?

Best Regards.

Dear Qlik Replicate Team,

We would like to request technical clarification regarding an Oracle CDC limitation in Qlik Replicate when replicating UPDATE operations on tables containing column names longer than 30 bytes.

1. Environment

Source Database: Oracle Database 19c

Qlik Replicate Version: 2025.11 SP06

CDC Method: Oracle Log Reader (Direct Redo Log Access)

Task Architecture: LogStream Staging Task → Replication Task

Oracle Parameter: ENABLE_GOLDENGATE_REPLICATION=FALSE

Supplemental Logging: ALL COLUMN

Table Characteristics: Contains one or more column names exceeding 30 bytes

2. Observed Behavior

When an UPDATE transaction is executed against the affected table, we observe the following behavior:

ALL COLUMN Supplemental Logging is enabled on the Oracle source database.

However, the Primary Key values are missing from the UPDATE event in the SOURCE_CAPTURE TRACE of the LogStream Staging Task.

As a result, the downstream Replication Task cannot properly construct the WHERE clause for the UPDATE statement in the TARGET_APPLY stage.

Consequently, the UPDATE operation cannot be applied successfully to the target database.

We have reproduced this issue with Qlik Replicate 2025.11 SP06.

3. Qlik Documentation

According to the Qlik Replicate Oracle Source Limitations documentation, Full Supplemental Logging is not available for tables containing column names longer than 30 characters when ENABLE_GOLDENGATE_REPLICATION=FALSE.

We also reviewed the Qlik Replicate May 2026 documentation and found that the same limitation still appears to be documented.

Therefore, it seems that this limitation has not been addressed in the currently documented product versions.

4. Comparison with Other CDC Solutions

We understand that other Oracle CDC products, such as Quest SharePlex and XLog, can support UPDATE replication for tables containing long column names even when ENABLE_GOLDENGATE_REPLICATION=FALSE.

Both products use direct Oracle Redo Log reading rather than Oracle LogMiner.

In particular, the Quest SharePlex Administration Guide documents a related Oracle key logging issue involving long identifiers and describes the SP_OCT_USE_SUPP_KEYS=0 setting as a workaround.

This suggests that different CDC implementations may use alternative approaches to selecting or processing key information for UPDATE operations.

5. Technical Questions

We would appreciate clarification on the following points.

Q1. Root Cause of the Limitation

Is the missing Primary Key information caused by Oracle not recording the required key values in the Redo Log, or by a limitation in Qlik Replicate's Oracle Log Reader when extracting or interpreting the Redo records?

Q2. Difference from Other CDC Products

Since other direct Redo Log Reader-based CDC solutions appear to support this scenario, could you explain the specific technical limitation that prevents Qlik Replicate from supporting it?

Q3. Alternative Key Handling Mechanism

Does Qlik Replicate provide an equivalent mechanism to SharePlex's SP_OCT_USE_SUPP_KEYS=0, allowing UPDATE row identification without relying exclusively on Oracle's supplemental key logging?

Q4. Workaround or Internal Parameter

Is there any supported configuration, Internal Parameter, Hotfix, or alternative capture mechanism that would allow UPDATE and DELETE replication for tables containing column names longer than 30 bytes while keeping ENABLE_GOLDENGATE_REPLICATION=FALSE?

Q5. Future Product Support

Is there any plan to address this limitation in Qlik Replicate 2026.5 SR1 or a subsequent release?

If an existing defect, enhancement request, or support case is associated with this limitation, could you provide the relevant reference number?

6. Request

Due to operational policies and potential Oracle licensing implications, enabling ENABLE_GOLDENGATE_REPLICATION=TRUE may not be feasible in our environment.

We would therefore like to understand whether Qlik Replicate can support this CDC scenario without changing the Oracle parameter.

If no supported workaround currently exists, we would appreciate an official explanation of the technical limitation and any potential plans for future enhancement.

Thank you for your assistance.

Best regards.

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!

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