Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio.
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics.
This blog was created for professors and students using Qlik within academia.
Hear it from your Community Managers! The Community News blog provides updates about the Qlik Community Platform and other news and important announcements.
The Qlik Digest is your essential monthly low-down of the need-to-know product updates, events, and resources from Qlik.
The Qlik Learning blog offers information about the latest updates to our courses and programs, as well as insights from the Qlik Learning team.
Effective in the Qlik Sense Enterprise on Windows November 2026 release, and in the latest patches for May 2025, November 2025, and May 2026, the ODBC connector used by Qlik Sense Enterprise on Windows will no longer support connections secured with TLS 1.0 or TLS 1.1. To maintain uninterrupted connectivity, customers should upgrade their environments to use TLS 1.2 or higher ahead of applying these releases or patches.
Refer to the release notes upon release of the affected versions for details.
TLS 1.0 and TLS 1.1 are legacy encryption protocols that are no longer considered secure and have been deprecated across the industry for several years. Removing support for these older protocols in the ODBC connector aligns Qlik's connectivity stack with current security standards and reduces exposure to known vulnerabilities in outdated TLS implementations.
This change affects the ODBC connector in Qlik Sense Enterprise on Windows only. At this point, Qlik Sense Desktop and QlikView are not affected by this change.
Any data source connection made through the ODBC connector in Qlik Sense Enterprise on Windows that relies on TLS 1.0 or TLS 1.1 will be affected once support is removed, regardless of whether the TLS version is enforced by the data source itself, a network intermediary, or the client driver configuration.
If your data source, ODBC driver, or the underlying operating system is currently configured to negotiate connections using only TLS 1.0 or TLS 1.1, those connections will fail once you move to a version of Qlik Sense Enterprise on Windows that removes TLS 1.0 or TLS 1.1 support.
Reload tasks, extensions, and any other workflows using affected ODBC connections will no longer be able to connect to the data source.
If you have questions or need assistance planning your upgrade, our forums are open to you, and Support is only a chat away.
Thank you for choosing Qlik,
Qlik Support
Sign up for the Private Preview and get hands-on with real-time Iceberg tables in your own Google Cloud project — no lock-in, no re-architecting.
If you're running analytics on Google Cloud, you already know the tension. BigQuery is fast and familiar, but the more data you pour into it, the more your ingestion and storage bill climbs, and the more your data ends up shaped around one engine. You want the performance without the lock-in, you want your data to stay yours, and you want to free up some budget for more valuable workloads.
That's exactly the problem Qlik Open Lakehouse solves — and we're getting ready to launch a Private Preview on Google Cloud this September that you can be part of.
Qlik Open Lakehouse gives you a fully managed way to ingest real-time data straight into Apache Iceberg tables that live in your own Google Cloud Storage buckets. No proprietary formats, no copies, no re-architecting your data layer. Query those same tables from BigQuery, Trino, or any Iceberg-compatible engine, and pay a fraction of what you'd normally spend moving and storing that data.
If you've followed our work on AWS, this will feel familiar — and that's the point. We're porting a proven architecture to Google Cloud, not building a science experiment.
Open Lakehouse builds the bronze layer of your medallion architecture, ingesting and landing real-time data as optimized Apache Iceberg tables, with the heavy lifting executed in your own Google Cloud project. From there, push-down transformations in Qlik Talend® Cloud pipelines create your silver and gold layers directly on BigQuery. Here's the path your data takes, stage by stage.
|
|
1 · Ingestion at the edgeYour sources land through two paths. For change data capture and bulk loads from databases, SAP, and mainframe systems, the Qlik Data Movement Gateway sits in your managed environment and handles CDC and bulk ingestion. For streaming and event data, you connect Kafka topics or Google Cloud Storage directly. Both routes feed the landing stage without your data ever leaving your control. Later in the Private Preview, we'll also add support for Qlik Replicate as a source, so if you're already a Replicate customer, you can onboard data from your existing CDC sources into Iceberg without migrating a single pipeline or switching tools. |
|
|
2 · Compute in your projectTwo components run on Google Compute Engine inside your environment. The Network Integration Agent runs on a standard Compute Engine VM and brokers secure connectivity between the Qlik Talend Cloud tenant and your resources. The Open Lakehouse Cluster — the engine that writes and optimizes your Iceberg tables — runs on a Compute Engine managed instance group built on Spot VMs. That Spot-based design is deliberate: it's where a large part of the cost savings comes from, because you're running the ingestion and optimization workload on Google Cloud's most cost-efficient compute instead of always-on, premium-priced infrastructure. |
|
|
3 · Open storage you ownEverything lands in Google Cloud Storage, split across a landing bucket for incoming data, a config bucket for pipeline metadata, and table storage where your data comes to rest as Apache Iceberg tables. These buckets are in your account. The data is written in an open table format from the start, so there's never a moment where it's trapped in something only Qlik can read. |
|
|
4 · A catalog any engine can useIceberg tables are registered in the Google Lakehouse runtime catalog, so your tables are discoverable and governable through Google Cloud's native catalog rather than a Qlik-proprietary one. That's what makes zero-copy querying real: BigQuery reads the same tables through ELT, and so can Trino or any other Iceberg-compatible engine, all pointing at one physical copy of the data. |
|
|
5 · A managed bronze layer, ready to build onThe pipeline moves through managed stages — landing, storage, and mirror — to produce clean, governed Iceberg tables without you hand-coding each hop. You get Type 1 and Type 2 slowly changing dimensions or append-only patterns out of the box, so history and current-state tables are handled for you. We'll also add zero-copy mirroring to BigQuery during the Private Preview, so you can surface your Iceberg data straight in BigQuery. If you want to replace an existing native table, you can, since downstream queries keep working exactly as before. |
The result: real-time data flows from your sources into governed, query-ready Iceberg tables in your own Google Cloud Storage, optimized continuously, queryable from BigQuery and beyond — and you never gave up control of a single byte.
We didn't start from zero for Google Cloud. Qlik Open Lakehouse first shipped on AWS, where it's already running these same patterns: CDC and streaming ingestion, Spot-based compute for cost-efficient optimization, Iceberg tables in customer-owned object storage, and open querying across engines.
Bringing it to Google Cloud is a deliberate step toward feature parity across clouds. The architecture mirrors what's proven on AWS, adapted to Google Cloud's building blocks: Compute Engine in place of EC2, Google Cloud Storage in place of S3, BigQuery and the Google Lakehouse runtime catalog as the native query and catalog layer. Same engine, same principles, GCP-native execution.
This matters because of what it says about our direction. We believe you should be free to choose where your data lives, which engine queries it, and to change your mind later without a migration project. Delivering the same open lakehouse capability across AWS and Google Cloud, with more to come, is how we make that freedom real rather than a slide in a pitch deck.
Everything above maps to three things we care about:
|
TRUST
Build governed data products in Qlik Talend Cloud on top of your Iceberg tables. Your data stays in open Apache Iceberg format, in your own account. |
FREEDOM
Query from BigQuery, Trino, or any Iceberg-compatible engine, and swap or add engines later without re-architecting. No lock-in to a single vendor or format. |
COST OPTIMIZATION
Spot VM compute and zero-copy, single-storage architecture mean you spend far less to move and hold your data at scale. |
We're accepting participants now, and we're prioritizing organizations already standardized on Google Cloud and working with BigQuery or Apache Iceberg in their accounts.
Request your spot in the Private Preview →Opt in through the form and the Qlik team will reach out to schedule a welcome call. Already signed up? Sit tight — we'll be in touch.
The Region Mover, available with the Qlik Talend Cloud Migration Toolkit (QTCMT), enables users to migrate a Talend Cloud (TC) or Qlik Talend Cloud (QTC) tenant to another Qlik Talend Cloud tenant while either remaining on Talend 7 or upgrading to Talend 8.
Before starting a migration, users can view the source tenant inventory directly in the Qlik Talend Cloud Migration Toolkit. This provides visibility into the currently existing assets and those available for migration.
The migration is organized into three steps:
For questions or assistance, please contact Qlik Support.
There are several scenarios where customers may need to move assets to a different region, including:
Region Mover enables faster migration, migrating assets to a new tenant more than 20x faster than performing the same migration manually, and significantly simplifies each migration step while giving you full control over exactly which assets get migrated.
Migration options include:
Download the latest release from the Migration Center page on Qlik Help.
Thank you for choosing Qlik,
Qlik Support
ブログ著者:Matt Hayes
本ブログは「Qlik Agentic Data Engineering is Generally Available. Here's What That Actually Means.」の翻訳になります。
4月に米国で開催された「Qlik Connect」の際、チームがパイプライン構築を超えて、自律的な AI エージェントを活用できる、信頼できるデータ基盤の設計へと向かっているという変化について、ブログを投稿しました。
そして現在、Qlik は、データチームがこの変化を認識する段階から、実際に運用する段階へと進むための支援を行っています。エージェンティックデータエンジニアリングの各機能が、Qlik Talend Cloud® において一般提供されました。
エージェンティックデータエンジニアリングは、2026年を象徴する話題の 1 つです。Gartner 社が 2026年 2月に発表した「Top Trends in Data & Analytics」レポートでは、2029年までに、適応性があり状況を認識する AI エージェントによるエージェンティックデータマネジメントが、データエンジニアリングのワークフローの 75% を自動化し、より価値の高い業務にリソースを解放すると予測されています。
この予測こそ、Qlik と今回のリリースが実現するものです。そして、私たちがデータを AI のために機能させているというもう一つの証明でもあります。
データエージェント
Qlik は、2026年 2月にエージェンティックエクスペリエンスを発表しました。今回のリリースでは、データエンジニアリングのワークフローに特化して構築された新しいエージェントによって、このエクスペリエンスをデータエンジニアリングの領域へと拡張します。
こうしたエージェントは、既存のワークフローの上に重ねられた単なる AI アシスタントではありません。自らの動作環境を理解し、関連するビジネス状況を処理した上で行動する自律した目標思考型のコンポーネントです。これこそが、「作業を助けるツール」と「共に働くシステム」との、アーキテクチャ上の決定的な違いです。
宣言型データパイプライン
お好みの統合開発環境上で、自然言語で Qlik のデータパイプラインを構築・更新することも可能になりました。現時点では、最も広く使われている組み合わせである、Claude Code または GitHub Copilot と VS Code の併用を推奨していますが、今後、対応する統合開発環境をさらに拡大していく予定です。
これからは、エンジニアが「意図」を記述するだけで完了できます。実装はコーディングエージェントが行います。本番投入前に手直しが必要な試作品ではなく、初日からガバナンスの効いた品質スコアが付与されたパイプラインを生成してくれます。
エージェンティックルーティングの強化
今回のリリースには、エンタープライズ向けのエージェンティックシナリオに対応する大幅に拡張されたコンテキスト・メモリウィンドウも追加されました。複雑な多段階のワークフローを構築するチームから最も多く寄せられていた要望に応えるべく実現しました。データの分類、セマンティックエンリッチメント、RAG パイプライン、そして動的ルーティングが、エンタープライズ規模の導入に求められるレベルで、事象主導型の統合フロー内で利用可能になりました。
上記の機能は、技術的な側面の回答です。より重要なのは、こうした機能がデータ基盤を運用する人や、それに依存するビジネスにとって、実際に何を意味するのかという点です。
データエンジニアまたはデータアーキテクトの方は…
現在、業務時間の大半を占めている、プロファイリング・カタログ整備・品質改良・パイプラインの展開や保守といった作業こそが、これらのエージェントが担うために設計された仕事です。エージェントは、あなたの役割を奪う脅威ではありません。エージェンティック時代が求めるレベルで業務を実行するために、生産性を飛躍的に高めてくれる力になります。
今後数年間で最も価値を発揮するエンジニアとは、新しいツールを活用できる人、そしてエージェンティックシステムが信頼し、その中で推論できるようなデータエコシステムを設計できる人です。彼らはコンテキストレイヤーを提供します。ガバナンスのガードレールを実装します。そして、あるフィールドを読み取った際に、生の値だけでなく、ビジネス上何を意味するのかを理解できるセマンティックな基盤を提供します。
さらに、宣言型データパイプラインで生産性を高めているコーディングエージェントを利用しながら、最初の確約段階から本番環境に耐えうる品質を保証することができます。あなたの業務内容が変わるわけではありません。働き方の効果を何倍にも高めるインフラを利用できるのです。
Head of Data / CIO / CDO の方は…
企業における AI への投資は、AI に提供されるデータの質に左右されます。目新しい指摘ではありませんが、エージェンティック時代においては、バッチ処理の時代のデータ問題とは比較にならないほど影響が即座に現れます。
人間のアナリストが不完全なデータを扱う場合、人間の判断力が働きます。なにかがおかしいと気づくことができますが、AI エージェントは気づくことができません。与えられたデータの品質を問わず、機械的に高速処理をします。「使用可能に見えるデータ」と「実際に使用可能なデータ」との間にあるギャップこそが、誰にも原因を特定されることなく AI の ROI が静かに失われていく原因です。
データ基盤が整えば、3 つの成果が変わります。
データに依存する業務を行う事業部門の方は…
オペレーション・財務・サプライチェーン・顧客対応といったチームが利用する AI システムは、利用するデータがビジネス状況に適しており、最新で品質スコアが付与されているほど、より的確な意思決定ができるようになります。現在、数値の正確性を疑ったり、異なるシステムから出てくる矛盾した結果を照合したり、データパイプラインの修正をデータエンジニアリングチームに依頼して待機することに費やしている時間こそが、今回のリリースで削減を期待できる「コスト」なのです。
パイプラインの時代が終わったのは、パイプラインが機能しなくなったからではありません。基盤が使う側の変化に追いつけなかったからです。
今回のリリースの決定的な違いは、Qlik Talend Cloud を利用していても、データが実際に存在するあらゆる環境で運用していても、後からデータ品質とガバナンスを追加するのではなく、最初から統合された形で提供しているという点です。
これが、「一般提供」という言葉が意味するところです。
When we introduced enhanced self-service scheduling in April 2025, we removed the When data is refreshed option, which had let reload schedules trigger automatically when a dependent dataset was updated. At the time, we weren't able to carry that capability forward into the new task-based scheduler right away.
That capability is now returning. See What's New in Qlik Cloud and Scheduling data refreshes with tasks.
In the task editor, under Based on > Event, you can now select When data is refreshed to trigger a task automatically when a data update is detected in an upstream Qlik Talend Data Integration project that loads data into an analytics application.
The option is only available if the application is connected to a Qlik Talend Data Integration pipeline.
This brings back the event-driven automation the old scheduler offered, now built natively into the new self-service scheduling framework, with full compatibility with the multi-task model.
If the application has an existing When data is refreshed schedule, this button might instead say Migrate. For applications with these schedules, clicking Migrate or Save will migrate all associated schedules to be individual tasks attached to the application.
No other action is required.
We're happy to assist with any follow-up questions. Reply to this blog post or take your queries to our Support Chat.
Thank you for choosing Qlik,
Qlik Support
Talking Heads sang "Once in a Lifetime" in 1980. Its central image - water flowing underground, endlessly, whether anyone's watching or not - was about sleepwalking through your own life while forces beneath the surface keep moving without you. It's also, unintentionally, a fair description of how enterprise data behaves: constantly flowing beneath the business, mostly unseen, doing its job whether a human ever looks at it or not. What's different isn't the flow. It's who's drinking from it. Qlik, SAP, and a cluster of vendors at API World have all recently opened the tap to a new consumer - AI agents -via a shared standard called MCP (Model Context Protocol). Same water. Different drinker.
Our recently launched Public Previews give you early, hands-on access to what's coming next in Qlik Cloud, before the previewed features are generally available. Try new capabilities, shape their direction with your feedback, and stay ahead of the latest features.
Public Previews are enabled by default for most users and are directly accessible from your profile:
A tenant admin needs to activate the feature preview program.
Read all about it in Introducing feature previews (Innovation Blog).
Getting started is quick and easy. Here is all you need:
Thank you for choosing Qlik,
Qlik Support
Qlik Automate's ServiceNow connector is moving from username and password authentication to OAuth 2.0. This change aligns with security best practices and ServiceNow's own recommendations for third-party integrations, eliminating the need to store credentials in plain text and providing more granular, revocable access control.
The change will go into effect on the 23rd of June, 2026.
Existing connections that use username and password authentication will need to be re-authenticated using OAuth 2.0. Complete the re-authentication steps as outlined in this blog post on the 23rd of June to prevent possible service interruptions.
ServiceNow provides guidance on each stage of the OAuth 2.0 setup. See the following for details:
To migrate your Qlik Automate connector, first prepare ServiceNow by configuring OAuth 2.0, then re-authenticate Qlik Automate on the 23rd of June.
Before you begin, make sure you have Admin access to your ServiceNow instance and Admin or Owner access to your Qlik Cloud tenant and the relevant Qlik Automate automation.
The OAuth 2.0 plugin must be available in your ServiceNow instance.
When prompted for a Redirect URL, use the callback URL provided by Qlik Automate during the connection setup. This URL must exactly match what is registered in ServiceNow.
This step can only be carried out after the change on the 23rd of June, 2026.
If you encounter issues during the migration, please contact Qlik Support or visit the Qlik Community for assistance. When raising a support case, include your ServiceNow instance domain and the error message you are seeing.
Thank you for choosing Qlik,
Qlik Support
On 13 August 2026, Kristu Jayanti University successfully hosted the third edition of the Qlik Datathon 2026, themed "Think Like a Manager." This flagship analytics competition brought together aspiring data professionals, encouraging them to apply analytics, artificial intelligence, and business thinking to solve real-world challenges.
This year's event marked a significant milestone as the first-ever inter-university Qlik Datathon, creating a larger platform for collaboration, innovation, and healthy competition among students from leading institutions.
Ask your coding agent a real question about your Qlik tenant and get a factual answer in real time. Qlik's MCP server now ships three new lookup tools purpose-built for declarative pipeline development, so Claude Code, Copilot, and Codex can check spaces, connections, and table structures against your live environment instead of guessing. No more tabbing out to the Qlik Cloud web app to hunt down a connection name or table ID, just faster, more accurate pipelines from the first prompt.
Qlik Talend Unlocked is a monthly series where engineers who have shipped this into production show you how. Each session takes on a real part of the modern Talend lifecycle, from CI/CD job promotion and test automation to migration, open lakehouse architectures, and real time integration. Practical approaches you can take straight back to your own environment, with results teams can measure.
Episode one is on demand now, episode two is open for registration. Register once and you are set for the whole series.
The World Cup is over, Spain are champions, and the third and final episode of our Model vs. Mastery podcast series has wrapped up with a verdict on the question we've been asking all along: when it comes to predicting football's biggest tournament, does the edge belong to the model or the human expert?
Host Adam sat down with Steve Palmer and Nick Magnuson to close out the series, and the results were more decisive than anyone on the losing end expected.