This month marks the public preview of the feature we've been building behind the scenes for many months, the most requested capability from our customers, and the one designed to fully unlock developer productivity: the Studio AI Assistant for Qlik Talend Cloud.

What's new

Built on Qlik Answers, the AI driven assistant in Studio turns your intent directly into Talend jobs, speeding up development across Jobs, Routes, and Data Services. Features include automated description generation, AI powered automap and mapping expression builder assistance, Java and SQL generation from prompts, and debug and troubleshooting support. As we move through preview, we'll iteratively expand these capabilities based on your feedback, including opening the scope to end-to-end pipeline building.

The contextual assistant window lives right beside your workflow, a native tool built directly into Studio. Here's what you can do in this preview launch:

• Document your work in one click. Ask your AI Assistant to generate a description and add it straight to your job.
• Shorten the time spent mapping complex schemas with AI powered automap and expression builder assistance.
• Generate SQL and Java from prompts wherever you need them, including components, routines, and beans in routes or jobs.
• Debug and remediate job failures. The assistant advises on critical runtime issues and provides solutions to fix and configure your jobs correctly.
• As the preview progresses, build increasingly complex jobs and routes directly from a prompt, using the catalog of assets already in Studio.

How to activate it

To activate this feature, work with your platform administrator. It's a three-step process:

• In Qlik Cloud, open Administration > Settings > AI features, and enable cross-region inference.

  For more information, see Enabling cross-region inference.

• In Qlik Cloud, open Administration > Settings > Tenant > Feature preview, and enable feature preview.

  For more information, see Enable feature preview for the tenant.

• Assign a new role to the user with the permission Features and actions > AI platform > Generative AI access set to Allowed.

  For more information, see Roles and permissions for users and administrators.

Documentation

AI assistant (Qlik Answers) in Talend Studio

How to share feedback

Your feedback is critical to this preview, and given the scale of this feature, we're running an extended preview period to give customers room to explore and report back. Once you've activated the preview, here's where to send your feedback. Our team is looking forward to hearing from you.

• Questions: post to the community forum.
• Bugs and issues: submit a case through our usual support channel, including your prompt, logs, and optionally your jobs or route. Please include "Feature preview" in the subject line so we can route your case to the preview team.

Hello,

I’ve configured a Log Stream task to read from a Microsoft Azure SQL database, along with a replication task that reads from this Log Stream and replicates data to a Databricks Lakehouse (Delta) endpoint.

Among the replicated tables, there is one with about 380 million records and 18 columns, which accumulates between 200,000 and 400,000 changes during the full load, which typically takes several hours.

Over the past few weeks, once the full load of this table completes, the task has been unable to apply the changes to Databricks. Specifically, the task tries to apply the DELETE operations on the table and remains in running state for tens of hours without completing the operation successfully.

The DELETE operation has this form:

DELETE FROM my_database.target_table T
WHERE EXISTS (
    SELECT C.seg1
    FROM my_database.attrep_changes_table C
    WHERE (
        T.primary_key = CAST(C.seg1 AS INT)
        OR (T.primary_key IS NULL AND C.seg1 IS NULL)
    )
    AND C.seq >= 1
    AND C.seq <= 200100
);

We have tried several alternatives to solve the problem, including:

• reducing the change batch size;
• increasing the query timeout of the operations;
• optimizing the large table to make delete operations more efficient;
• replicating only the last 6 months of data for the large table.

Unfortunately, none of these attempts was successful.

However, we verified that the following DELETE operation runs in 30 seconds on Databricks:

DELETE FROM my_database.target_table
WHERE primary_key IN (
    SELECT CAST(seg1 AS INT)
    FROM my_database.attrep_changes_table
    WHERE seq BETWEEN 1 AND 200100
      AND seg1 IS NOT NULL
);

Is it possible to configure the replication task to run DELETE operations using the syntax above?

I understand that Qlik Replicate provides internal parameters to customize the SQL syntax it generates, such as $info.query_syntax.create_table for table creation. Is there an equivalent parameter for DELETE operations? If so, how could we set it so that the task uses the syntax shown above? If no such parameter exists, is there an alternative way to achieve the same result?

Thank you in advance for your support.

Best regards

Hi,

We are hitting an issue where table names containing non-ASCII characters (Norwegian Ø) fail against a Databricks Lakehouse (Delta) target. The character survives DDL generation but is corrupted in the metadata lookup, so Replicate cannot find the table it just created.

Qlik Replicate: 2026.5.0.169, Windows
Source: IBM DB2 for LUW via Log Stream
Target endpoint: Databricks Lakehouse (Delta), Unity Catalog enabled, staging type Databricks Volume
Databricks ODBC driver: 2.10.0.1002 (64-bit)

DETAILS:

CREATE TABLE sends the correct UTF-8 name:
CREATE TABLE `[REDACTED]`.`transportør` ( `transportør` DECIMAL(6,0) NOT NULL, ... ) USING DELTA

DESCRIBE TABLE sends a corrupted name:
09:12:34 Failed to DESCRIBE TABLE
SqlState: 42P01 NativeError: 80
[TABLE_OR_VIEW_NOT_FOUND] The table or view `[REDACTED]`.`transport?r` cannot be found.
Failed to get table transport?r definition
Table '[REDACTED]'.'transport?r' does not exist, insufficient privileges or no supported columns

Because the lookup fails, Replicate treats the table as new, skips the drop, and issues CREATE, which then fails:
SqlState: 42P07 NativeError: 35
[TABLE_OR_VIEW_ALREADY_EXISTS] Cannot create table or view `[REDACTED]`.`transportør` because it already exists.

The table is suspended and never loads. Tables without Ø in the name work normally in the same task.

VERIFIED
- The character is a normal U+00F8. Verified in Databricks: hex(column_name) returns C3B8, identical in both schemas.
- Column names with æ/ø/å work fine. For example, `transportør` are created and populated correctly as columns.
- The Replicate user has full privileges on the schema. Manual DROP TABLE from the Databricks SQL editor succeeds.
- The target tables were dropped manually before retrying, so TABLE_OR_VIEW_ALREADY_EXISTS is not caused by leftover objects.

ALREADY TESTED, NO EFFECT
1. Global rule RENAME_TABLE with expression:
replace(replace(replace(lower($AR_M_SOURCE_TABLE_NAME),'Æ','æ'),'Ø','ø'),'Å','å')
This produces the correct lowercase name in CREATE TABLE, but DESCRIBE TABLE still sends transport?r.
2. Server setting "Support special characters in column names used in expressions".
3. Databricks ODBC DSN option "Unicode SQL character types" (UseUnicodeSqlCharacterTypes), with a restart of the Replicate service.

QUESTIONS
1. Is there an internal parameter on the Databricks Lakehouse (Delta) endpoint that controls character encoding for identifiers in metadata queries, so non-ASCII table names survive the DESCRIBE TABLE lookup?
2. If not, can you confirm this is the documented ASCII limitation for the Databricks target, and whether support for non-ASCII table names is on the roadmap?
3. Is the inconsistency itself considered a defect? The same task encodes the same table name correctly in DDL and incorrectly in metadata lookups.

We are applying an ASCII transliteration of the table names as a workaround so the tables load, but we would prefer to keep the original names.

I am building a CDC pipeline using Qlik Replicate May 2026 and Talend Studio R2026-05:
     Oracle -> Qlik Replicate -> S3 Parquet -> Talend Big Data Batch job -> Apache Iceberg

Spark + Apache Iceberg natively supports MERGE INTO, UPDATE, and DELETE.

However, in Talend Big Data Batch job, tIcebergSQL component appears to support only Create Namespace, Select, and Insert, while tIcebergMerge component is available only for Standard jobs.

Is there a supported way to execute native Iceberg MERGE INTO from a Spark Batch job without staging the data and invoking a separate Standard job?

If not, is Big Data Batch job support for tIcebergMerge or MERGE INTO in tIcebergSQL on the product roadmap?

2026年9月30日(水)に開催した無料Webセミナーの資料です。
QTCの「Data Movement Gateway」で「Apache Kafka」をレプリケーションターゲットに使用する ～PythonやTalend Studioでコンシューマも作成～
https://techplay.jp/event/1000565
Qlik Talend Cloudの「Data Movement Gateway」サーバーを利用すれば、オンプレミスのRDBMS(例:MySQL等)のデータをレプリケーション(Full　LoadおよびCDC)するストリーミングターゲットとして、「Apache Kafka」や「Amazon MSK」を使用することが可能です。
レプリケーションされたデータは、Kafkaのコンシューマを作成して受信することにより、データの内容に応じて様々な処理へと連携させることが可能になります。
この資料では、MySQLのデータをData Movement Gatewayを介してApache Kafkaにリアルタイムにレプリケーションし、PythonやTalend Studio(標準ジョブやRoute)でコンシューマを作成する方法について説明します。

Hello , I have a Button object in Qlik Sense . I want to display a tooltip text when hovering the mouse over the button (for example : display "Mobile" when hovering the Mobile button).

Hi Team,
we are planning for LV automation in Qsense, need a Qsense APIs to hit QMC to get the info of stream, owner, name, created date. And to download dashboard as pdf.
Please help to provide the relevant APIs to do the above activities.

Hi,

How does increasing the readAheadBlocks internal parameter on an Oracle source endpoint increase the memory usage on the Oracle server machine? Thanks

Regards,

Mohammed

We're challenging our Qlik Community: put agentic AI to work. 

We saw lots of great posts in our recent Make Your Data Work for AI forum. We’re building on that momentum with a new board focused on the next step: driving real impact with agentic AI.

This is the place to get started with agentic capabilities, try them out, and share your experience with the rest of the Community.

Here's the challenge:

1. Get started. Toggle on Qlik Answers, activate Qlik’s MCP Server, or get started with whichever capability fits your work, and see how easy it really is.
2. Build your first workflow. Identify a use case and put the capabilities to work on a real problem or task.
3. Share your experience. Tell the Community what you learned, what worked, and what surprised you.

Ask questions, share screenshots (obscuring any sensitive data), get ideas, and help your Qlik Community peers on their journeys.

You'll earn NEW Community badges along the way: Agentic AI Adopter when you share your first workflow or use case, and Agentic AI Expert when you share your learnings and results.

Plus, we’ll be awarding some fun surprises and new Qlik swag along the way!  

I am going to retrive metadata of a qlikview files existing in an organization server.
i wanna declare a connection and extrac all thier metadata.
but i didnt find any way from qlikview to expose metadata of thier dashboard and reports.
is there any body who did that?

Is it possible to per default disable the data preview when opening the script editor on a Qlik Sense on Windows installation?

When a developer navigates to the Data Load Editor of an Qlik Sense application then the default view is to see script section to the left, the data connections to the right and the data preview tables in the bottom. Populating these views, sometimes  makes the data editor page use substantial amount of time to fully render it self so it is possible for the developer to do script changes or initiate a reload.

We handle some very large applications and we believe being able to disable the data preview in the load script editor would speed up the rendering of the load script editor page. 

I have not found any documentation on how to set the default state to disable disable the preview. Is it possible to configure Qlik Sense to do this, either on environmental or by app level. 

(The environment is running Qlik Sense November 2024 on multiple nodes)

Hi,
We are facing the issue with context menu after upgrading Qlik Sense Enterprise from November 2025 to May 2026 version.
Users can't export data anymore.
We just tried using different versions of iOS (even the latest one 27) but the problem is still unresolved.
We are using both SAFARI and CHROME browser on iPad 9.
Long-touching a visualization (ex. pivot table) should open the options menu, but it doesn't.
How it could be fixed? @Daniele_Purrone 
Please let me know.
Best Regards

Hi all, good evening,

I need to compare the cumulative sales between a year and the year before. This for many years stored in my database.

The sales had already been normalized by the month of each year.

This is the expression I created to generate the information for each year:

Aggr(RangeSum(Above(Sum(QTY), 0, RowNo())), [SALES YEAR, [YEAR/MONTH])

And this is the generated graphic:

What I need is to created a new graphic that shows, for each year, the % growth between that year vs its last year, using the same rule (acumulated sales for each month).

I have already tried many solutions here in the topics, but I couldn't get the right result.

For exemple: Aggr(RangeSum(Above(Sum(QTY) / Sum({<[SALES YEAR] = {"$(=Only([SALES YEAR])-1)"}>}QTY), 0, RowNo())), [SALES YEAR, [YEAR/MONTH])

Thanks in advance for any help.

Hi everyone,

I am facing a critical security concern regarding Section Access and Binary Loads, and I would like to know if there is a way to prevent it.

The Scenario: I have a base application with Section Access properly applied to restrict data visibility. Another developer user consumes this app's data model using a Binary Load.

The Problem: The issue happens when this developer uses the STORE statement in their script to export the loaded tables into QVD or TXT files. The exported files are created without any access restrictions. The Section Access rules are completely bypassed in the stored data.

The Security Concern: Because of this behavior, a developer can easily extract restricted data into unrestricted files. I consider this a severe security risk and data leakage problem, and I am very concerned about the platform's data governance in this scenario.

My Questions:

1. Is there any way to block, disable, or restrict the use of the STORE command for developers who are using a Binary Load?

2. Are there any configurations, security rules, or best practices at the QMC/Tenant level to prevent this specific type of data extraction?

I understand that we could segregate access using Spaces. However, these developers need to access the data spaces to perform the Binary Load and consume the data model. Even if we restrict their write access to corporate Shared/Data Spaces, they might still be able to STORE the data into their Personal Spaces. How do you handle this architectural dilemma without completely stopping the use of Binary Loads?

Any insights or workarounds to secure this architecture would be greatly appreciated.

Thanks in advance!

Hi,

Thank you

Qlik is pleased to announce the general availability of the Qlik Sense Content Monitor v1.2.0. This version is only made available on the Qlik Downloads page for manual deployment. It should work on Qlik Sense versions from February 2020, but support is provided only to the version deployed by the installation or upgrade of Qlik Sense.

It extends the previous version with the inclusion and display of:

• Flag on the Applications table indicating if the app reloads using Binary
• Flag on the Applications table indicating if the app is used by Mashups
• Flag on the Applications table indicating if the app uses “Lib Connect”, e.g. it reads from external sources (databases, APIs, etc.)
• New sheet listing Load Balancing Rules
• New sheet listing Security Rules
• New sheet listing Users, with details and counts on User Directories and User Groups
• New sheet listing Custom Properties and Custom Property values, and their relationship with Users, Streams, Apps, Nodes, Extensions, Tasks, Load Balancing Rules and Security Rules
• New sheets listing Custom Properties alongside Users and User Groups
• Improved data load script to recover data from failed reloads
• Improved data load script to avoid unnecessary log files crawling
• Added a variable for the use of a custom REST connection
• Strengthen the code to move-on even if the Qlik Sense version can’t be found in the logs
• Adds a flag to the Qlik Sense Object Scanner to automatically enable the attachement of Parquet files to Apps

It includes other improvements and minor bug fixes. 

Because this version is not yet part of a Qlik Sense release, the Content Monitor help page and Qlik Sense Object Scanner help pages include specific call-outs for functionality related to this version.

More configuration and troubleshooting details can be be found in the documents included in the download package.