Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Forums for Qlik Analytic solutions. Ask questions, join discussions, find solutions, and access documentation and resources.
Forums for Qlik Data Integration solutions. Ask questions, join discussions, find solutions, and access documentation and resources
Qlik Gallery is meant to encourage Qlikkies everywhere to share their progress – from a first Qlik app – to a favorite Qlik app – and everything in-between.
Get started on Qlik Community, find How-To documents, and join general non-product related discussions.
Direct links to other resources within the Qlik ecosystem. We suggest you bookmark this page.
Qlik gives qualified university students, educators, and researchers free Qlik software and resources to prepare students for the data-driven workplace.
Previously, the /api/v1/apps endpoint could be used to list all apps on a tenant. This method has always been unsupported and undocumented, and will be removed in the first week of May 2026.
If you are currently using /api/v1/apps, switch to GET with /api/v1/items instead.
This can be further filtered by choosing a resource type (such as /items?noActions=true&resourceType=app, /items?noActions=true&resourceType=script, or similar).
For more information, see:
If you have any questions, we're happy to assist. Reply to this blog post or take your queries to our Support Chat.
Thank you for choosing Qlik,
Qlik Support
Are you still looking to convert your QlikView environment to Qlik Cloud, but find the concept of migrating each of your apps daunting? Then Qlik has the answer for you.
QlikView to Qlik Sense Converter Tool – SaaS in 60
We've introduced the QlikView to Qlik Sense Converter Tool (QV2QS), which delivers ready-to-use Qlik Sense apps complete with sheets, layout, expressions, and data. Better yet, it deploys them directly to your Qlik Cloud tenant, all of which reduces your conversion times from hours to minutes.
Developed and supported by Qlik, QV2Q can:
While other converters produce master items from a subset of charts and tables (no sheets, no layout, no text objects, buttons, containers, or backgrounds), QV2QS delivers complete, ready-to-use apps.
Not only that, but migrating to Qlik Cloud using QV2Q2 will also enable you to:
QV2QS is built for Qlik consultants, QlikView developers, Qlik Sense developers, BI teams, and IT administrators migrating from QlikView to Qlik Sense. QV2QS runs as a standalone Windows executable with two interfaces: a guided web-based wizard and a command-line interface.
Here's what you will need:
Thank you for choosing Qlik,
Qlik Support
Beginning on April 14, 2026, multiple QlikView customers experienced outages and intermittent disruptions within their QlikView environments. These incidents coincided with the deployment of Microsoft’s April 2026 security patches to Domain Controllers, which affected QlikView Server Service (QVS) communications over port 4747.
The Microsoft patches introduced changes targeting Kerberos authentication and RC4 encryption. See Addendum for a list of patches. As a result, QlikView environments where RC4 remained enabled (such as at the domain account or Windows server level) became unstable or non-functional.
The impact on QlikView may include, but is not limited to:
Temporary mitigation measures have included rolling back the Microsoft patches on Domain Controllers, redirecting QlikView servers to unpatched controllers, and applying configuration changes such as removing RC4 ciphers and resetting QlikView service account credentials. These approaches have yielded partial success, particularly in older QlikView deployments.
For information from Microsoft on how to address the issue, see Detect and remediate RC4 usage in Kerberos.
Qlik Support is actively investigating and working to reproduce the issue across different customer scenarios to further validate root causes and identify consistent solutions. Subscribe to this blog post to be alerted when additional information is available.
RC4 support was deprecated starting with the May 2024 release of QlikView. The root cause in these cases stems from legacy configurations where RC4 remained enabled in the environment, rather than a defect in QlikView itself. No code changes are planned at this time, though improvements to diagnostic logging are under consideration.
Microsoft Patches:
If you have any questions, we're happy to assist. Reply to this blog post or take your queries to our Support Chat.
Thank you for choosing Qlik,
Qlik Support
Hi everyone,
Want to stay a step ahead of important Qlik support issues? Then sign up for our monthly webinar series where you can get first-hand insights from Qlik experts.
This Thursday, April 30 Qlik will host another Techspert Talks session and this time we are looking at Migrating QlikView to Qlik Cloud.
But wait, what is it exactly?
Techspert Talks is a free webinar held on a monthly basis, where you can hear directly from Qlik Techsperts on topics that are relevant to Customers and Partners today.
In this session we will cover:
Choose the time that's best for you
The webinar is hosted using ON24 in English and will last 30 minutes plus time for Q&A.
Hope to see you there!!
Update March 4th, 2026: added link to How to get Talend Management Console task schedules and pause and resume during a maintenance window using the API article
Updated April 24th, 2026: added impact on APIs (all down) and additional clarification on why tasks must be stopped and the impact on remote engines
Talend Cloud and Talend Management Console will undergo scheduled maintenance in March, April, and May. This infrastructure modernization is a key step in unifying the Talend ecosystem with Qlik.
The alignment paves the way for a more seamless experience across both platforms. Over the coming months, you will gain access to integrated features that bridge data integration and analytics, enabling unified governance and a streamlined management experience across your entire data lifecycle.
The maintenance windows will occur per region, during off-peak hours, and are expected to have a maximum of 30 minutes of effective downtime.
A full outage of Talend Cloud and Talend Management Console for a duration of up to 30 minutes within a preplanned 4-hour window.
The following applications will not be accessible:
All APIs for Talend Cloud will not be available during the outage. APIs impacted:
In detail:
It is recommended to pause existing task runs during the maintenance window. Talend Remote Engines will continue processing tasks during the outage if they started before the maintenance window, but as they may have inconsistent statuses, we recommend pausing all tasks beforehand.
This concerns all jobs and plans scheduled to start or run during the maintenance window.
See Checking scheduled task runs against your maintenance timetable on how to identify these plans and jobs.
Looking for information on how to identify, pause, and resume your tasks? See How to get Talend Management Console task schedules and pause and resume during a maintenance window using the API.
Each region will undergo maintenance for 4 hours during off-peak hours, with a maximum of 30 minutes of effective downtime.
| Region | Maintenance Start | Maintenance End |
| Talend Cloud - AWS - Asia Pacific (Sydney) au.cloud.talend.com |
UTC: 25/03/26 - 11:00 |
UTC: 25/03/26 - 15:00 |
| Talend Cloud - AWS - Asia Pacific (Tokyo) ap.cloud.talend.com |
UTC: 20/04/26 - 13:00 |
UTC: 20/04/26 - 17:00 |
| Talend Cloud - AWS - US East (N. Virginia) us.cloud.talend.com |
UTC: 27/04/26 - 6:00 |
UTC: 27/04/26 - 10:00 |
| Talend Cloud - AWS - Europe (Frankfurt) eu.cloud.talend.com |
UTC: 26/05/26 - 19:00 |
UTC: 26/05/26 - 23:00 |
To identify which region your tenant is affected by, cross-reference Accessing Talend Cloud applications.
To track further updates during the scheduled Qlik Cloud Maintenance, please visit our Qlik Cloud Status page. This blog post will be updated with additional information where necessary.
Thank you for choosing Qlik,
Qlik Support
As a follow-up to my previous blog post titled Finance Report with Waterfall Chart, I wanted to share an awesome demo that showcases financial reporting visualizations including a profit & loss statement with a waterfall chart. Qlik's Dennis Jaskowiak and Ekaterina Kovalenko, and partner Dawid Marciniak from HighCoordination, created the Financial Analysis demo based off of Jedox data, incorporating many enhancements to the straight table and pivot table. In addition to the waterfall chart, they use inline SVG to create lollipop charts and bar charts in financial statements.
Here is a look at some of the sheets:
The Dashboard provides a high-level overview of profit and loss, cash flow and liquidity. On this sheet, view the use of inline SVG bar charts and lollipop charts.
The P&L sheet provides a more detailed look at profit and loss.
The Cost Center sheet uses the pivot table to show sales costs.
Find a detailed look of cash flow on the Cash Flow sheet.
This is just some of the sheets you will find in the Financial Analysis demo. If you are looking for appealing ways to visual your financial data while keeping it concise and clean, download the Financial Analysis demo here.
Thanks,
Jennell
With less than 50 days to go before the 2026 World Cup kicks off across the US, Canada, and Mexico, I wanted to share a project I've been working on that brings together a few pieces of the Qlik platform I think work really well together: Choose Your Champion 2026.
It's a web app where anyone can fill out their World Cup bracket, get AI-powered predictions for every possible matchup in the tournament powered by Qlik Predict, explore historical World Cup data, and compete on a leaderboard as the competition unfolds.
You can try it here: https://webapps.qlik.com/choose-your-champion-2026/index.html#/
The app is powered by Qlik, with Qlik Cloud Analytics for the data model and Historical Analysis, Qlik Predict for the matchup predictions, and various Qlik APIs to wire everything into a React front-end.
In this post, I'll walk through how the predictions work under the hood, because that was the most interesting piece to build.
Choose Your Champion is broken into 4 parts:
This was the fun part. The goal was simple, given two national teams, predict the outcome of a hypothetical match (team A wins / draw / team B wins), but the work that makes the predictions actually useful is mostly in the data, not the model (thanks to no-code ML with Qlik Predict).
1. The training dataset
I started with every international football match result from 1872 to March 2026. There's a well-maintained open dataset on GitHub (credit: martj42/international_results) that gets updated after every international window, about 49,000 matches in total.
From that raw history, I built a training dataset focused on the modern era (2010 onwards) and only competitive matches (qualifiers, continental tournaments, World Cup finals). Friendlies got filtered out because they're noisy since teams often don't play their A squads, and the stakes don't match what happens in a real tournament.
That left me with around 9,400 training rows, each representing a real historical match with a known result, enriched with 27 features describing both teams' state going into that match:
2. ML Experiment
Once the training CSV was in shape, I uploaded it to Qlik Predict, pointed at the result column as the target, and let it do its thing. This is where Qlik Predict really shines, zero code needed. No Python notebooks, no sklearn, no hyperparameter grids to tune. You just upload your data, pick a target, and it does the heavy lifting with full explainability on the outcomes and what drives the predictions.
Qlik Predict runs multiple algorithms in parallel: LightGBM, CatBoost, XGBoost, Random Forest, and a few others, tunes their hyperparameters, and picks the best performer by F1.
On my first run, I left all the columns in the dataset checked, including the team name columns (team_a, team_b). When I looked at the SHAP importance chart afterward, team_b and team_a were ranking as the #2 and #3 most influential features, meaning the model was essentially learning "team X usually wins" rather than learning from the engineered features.
I created a new version, went back to the Data tab, unchecked the team name columns and a few date fields (which were also ranking higher than they should), and re-ran the experiment. Qlik Predict automatically dropped several more low-importance features during training, leaving a clean, focused feature set. The F1 did not change a lot (stayed at ~0.50), but the SHAP chart now showed the model leaning on exactly the signals we want:
A few other calls that mattered:
3. The apply dataset
Training gives you a model and to use it, you need an apply dataset with new rows you want predictions for.
For Choose Your Champion, I generated every possible pairing of the 48 qualified teams, which comes out to 1,128 unique matchups. Each row has the same 27 features as the training dataset, but computed as a current snapshot: each team's Elo today, their current FIFA ranking, their most recent 10-match form, and so on.
I fed that into the deployed model and got back a probability distribution for every matchup: P(team_a_win), P(draw), P(team_b_win).
The web app is a React front-end that connects to the Qlik tenant over anonymous access via @qlik/api, so users never see a login screen or have to authenticate against a tenant. The bracket UI pulls predictions from the Qlik Sense data model, so whenever a user opens a matchup, they're looking at data straight from Qlik.
For the historical World Cup section, I used a mix of @qlik/embed components when I needed a quick, ready-to-use chart, and custom nebula.js + picasso.js visualizations when I needed more control over the styling to match the app's look and feel. Both approaches work against the same underlying Qlik Analytics app, so everything stays consistent and governed in one place.
If you're thinking about building something similar, a few things worth keeping in mind:
Spend the time on feature engineering. The difference between a model that predicts noise and one that predicts football is almost entirely in the features. Qlik Predict handles algorithm selection and tuning well, but it can only work with what you feed it.
The integration is where Qlik Predict pays off. Once a model is deployed, scoring a new dataset and pulling scores back into a Qlik Cloud Analytics app takes one load script. No Python services to maintain, no separate MLOps platform to stand up, no JSON plumbing between systems. That end-to-end data prep, modeling, predictions, and analytics all living in one platform is the thing that made this project come together fast!
The World Cup starts June 11, so there's plenty of time to get your bracket in and earn your spot on the leaderboard before kickoff. If you're curious about how any of this was built, leave a comment or reach out to me directly!
And if you want to learn more about Qlik Predict and start using it, visit: https://www.qlik.com/us/products/qlik-predict
P.S: I have attached both Training and Apply datasets if you'd like to use them in your own Qlik Predict experiment.
Thank you!
Salesforce is rolling out mandatory security updates to how connected apps handle OAuth authentication.
To keep your Qlik Automate Salesforce connector working after Tuesday, 5th May 2026, you'll need to take a quick, one-time action: update a setting in your connection and re-authenticate to Salesforce.
This cannot be done automatically, nor can it be done before the release. A manual step is required on or after the 5th of May.
Salesforce has updated its OAuth security requirements for connected apps. You can read Salesforce's full announcement here: Mandatory Security Updates for Connected Apps.
Qlik Automate has updated the Salesforce connector to comply with these new security requirements. However, because of the nature of this change, existing connections cannot be migrated automatically.
Follow these steps after the release on Tuesday, the 5th of May:
If you don't complete these steps after the release date, your Salesforce automations will stop working and return a 401 Unauthorized error. No data will be lost, but you will need to complete the steps above to restore access.
If you have any questions, we're happy to assist. Reply to this blog post or take your queries to our Support Chat.
Thank you for choosing Qlik,
Qlik Support
We’re excited to announce a major step forward in making Qlik Learning more accessible, personalized, and impactful; translations are now available for all users. Our first stop is France.
Your feedback drives this launch. One of your top requests was learning in your preferred language, and today we’re making that happen.
To accelerate availability, we’re leveraging machine learning–based translation technology to quickly bring essential content to more learners around the world. We’re kicking things off with our first set of courses in French, followed by Japanese, Italian, and many more languages coming soon.
🌐 Getting Started
Changing your language is simple:
⚠️ What to Expect
🛠️ Additional Notes
We truly appreciate your feedback and patience as we continue to evolve. To provide feedback, click the stars
at the top of this page and share your feedback with us.
We hope you enjoy Qlik Learning in the language that works best for you!
Something quietly remarkable happened in the first quarter of 2026. While the public conversation was still asking whether AI agents would really change business, Gartner reported that 40% of enterprise applications are expected to integrate task-specific AI agents by the end of 2026, up from less than 5% a year ago. G2's August 2025 survey of enterprise buyers found that 57% of companies already had AI agents in production, not as chatbots, but as autonomous systems executing workflows, monitoring compliance, and coordinating decisions across business functions.
For those of us who work at the intersection of data, analytics, and higher education, this isn't a distant trend. It's a curriculum question.
For two decades, the defining promise of business intelligence has been "self-service analytics", empower every user to query, visualize, and explore data themselves. In the agentic era, the paradigm changes. AI agents are not a new tool in the analyst's toolkit; they are analysts. They plan multi-step tasks, call APIs, reason across data sources, and increasingly execute actions without waiting for a human prompt.
At Qlik Connect 2026, the message was direct: enterprises are closer to agentic AI than they think, because the foundation they already built, governed data, trusted metrics, clear business logic — is exactly what agents need to operate reliably. In February, the general availability of Qlik's Model Context Protocol (MCP) Server made it possible for third-party assistants, including Anthropic's Claude and OpenAI's ChatGPT, to access governed enterprise data through Qlik's APIs rather than scraping dashboards. The dashboard is no longer the endpoint. It's one of many surfaces where a decision gets made.
Here is the uncomfortable reality: Gartner projects that over 40% of agentic AI projects will fail by 2027, not because the models aren't capable, but because legacy systems, poor data architectures, and weak governance can't support autonomous execution. Deloitte's 2026 State of AI in the Enterprise report, based on a survey of 3,235 leaders across 24 countries, found that only 25% of organizations have moved 40% or more of their AI pilots into production, and just 21% have a mature governance model for autonomous AI agents.
The scarce capability is no longer "who can build a dashboard." It is:
These are not niche skills reserved for data engineers. They are the new baseline for anyone graduating into a workforce where, by 2028, Gartner estimates 15% of day-to-day decisions will be made autonomously.
This is where Latin America has a genuine strategic window. Our universities often face the critique of "catching up" on technology adoption. In the agentic era, that framing is misleading, the agentic shift resets the starting line for everyone. Institutions, anywhere in the world, that graduate students fluent in data governance, explainable AI, and human-agent collaboration will be the ones supplying the talent that enterprises are already scrambling to hire.
According to DataCamp's 2026 State of Data & AI Literacy Report, 88% of enterprise leaders say basic data literacy is important for day-to-day work, 60% report a data skills gap in their organization, and organizations with mature literacy programs are nearly twice as likely to see strong AI returns. The companies that will hire our graduates next year are telling us, in plain terms, what they need.
Three practical moves that don't require launching a new degree program:
The agentic era will not be defined by which models win. It will be defined by which people, and which regions,learned to work alongside them first.
By giving students, professors, and universities free access to analytics software, learning content, and certifications, the Qlik Academic Program helps education stay aligned with the data trends shaping 2026 and prepares learners for the jobs of tomorrow.
Join our global community for free: Qlik Academic Program: Creating a Data-Literate World
In our increasingly globalized environment, enabling seamless multilingual support in your Qlik Sense apps is no longer a nice-to-have - it’s expected.
Many implementations require users to manually select their desired language to display labels and content. In a helpful Qlik Community post, Jennel guides users through building a multilingual Qlik Sense app using an Excel-based translation table and manual language selection via dropdowns.
While Jennel’s solution is powerful and flexible, it relies on users making that initial language choice. In this article, I’ll show how to streamline the user experience by automatically detecting a user’s preferred language - based on their Qlik Cloud profile - and dynamically adapting the app accordingly using the GetUserAttr('userLocale') function.
Jennel’s method involves:
This approach, while widely used, introduces a required step - it depends on users selecting their preferred language every time they open the app.
My solution builds on Jennel’s foundation with one key improvement: the app automatically reads the user’s preferred language from their Qlik Cloud settings via the newly added attribute to the GetUserAttr: userLocale. This eliminates manual language selection and delivers an interface that adapts instantly and seamlessly to each user.
In the Data Load script, nothing really changes from Jennel’s approach: I loaded an external file containing the required translations:
The magic happens in the front-end part of the analytics app. Everything that should be translated uses the same approach that Jennel stated in her article: a variable with a Set Analysis filter containing the ID of that specific label/title/subtitle.
={<Index={46}>} $(vLanguageString)
The magic is in the variable; $(vLanguageString), in fact, is defined as:
vLanguageString = Only({<Language={"$(vUserLanguage)"}>} Translation)
Please note the use of another variable called “vUserLanguage”: the usage of a nested variable allows to manage situations in which the user locale is not included in the translations table. Let’s say a user has Qlik Cloud set in Spanish but Spanish translations are not available: in this case the app would display everything in English despite the user locale selection.
The variable “vUserLanguage” is defined as follows:
vUserLanguage = if(count({<Lang={"$(=GetUserAttr('userLocale'))"}>} Lang) = 0, 'en', GetUserAttr('userLocale'))
As you can see, I used GetUserAttr(‘userLocale’) to fetch the preferred language set by the user in their Qlik Cloud profile. Doing this, automatically sets the translation to the user’s preference without any manual intervention.
The field “Lang” is in a dedicated table I created in the Load Script that contains all the languages available in the translations table:
To give users feedback regarding the current language, I used a flag image conditionally displayed in the app by leveraging a Layout Container. Layout Container, in fact, can conditionally display elements inside them: I then defined the conditional display rule as follows.
=$(vUserLanguage) = 'de' for German Flag
=$(vUserLanguage) = 'en' for English Flag
=$(vUserLanguage) = 'it' for Italian flag
An alternative solution could be to use a KPI with a conditional background image, using the string returned by GetUserAttr as part of the image name. Note that I used the “vUserLanguage” variable to ensure that we catch the default in case user locale is not available in the translations table.
Accessing the app with locale set to “English” displays all labels and titles in English:
Let’s go to my Qlik Cloud profile and changing locale to “Italian”:
Re-accessing the app displays labels and titles in Italian (check the flag on top right!):
Easy, without any additional effort!
Hope this article inspires you to build multilingual apps with this new feature!
Qlik constantly refines its Analytics, over time replacing old charts with new, modernized alternatives. These deprecations are announced well in advance and come with instructions on how to best replace these old charts, whether that is to use a new one, several new ones, or make use of new settings.
This blog post covers the deprecation of charts in May 2027 and offers you guidance on how to replace them.
The following seven visualization bundle charts are up for deprecation in May 2027. Most have already been removed from the asset panel and are no longer a part of recent applications.
Since these are old charts, most are no longer in use. If you happen to still have a very old application and need to replace deprecated charts, see Visualization bundle > Deprecated charts for more information on what to use instead.
Qlik recommends reviewing your apps for old charts. Depending on your platform (Qlik Cloud or Client-managed), there are different methods you can deploy.
Qlik Cloud administrators should use the Qlik Cloud Monitoring Apps to track the usage. The App Analyzer has a sheet dedicated to where deprecated charts are being used on a tenant in Qlik Cloud. The App Analyzer is based on usage events rather than scanning every app. Use the App Analyzer to find which apps and sheets have charts that need to be updated to newer and more modern alternatives. The easiest way to install and update the Qlik Cloud Monitoring Apps is to use the automation template. If you already have the App Analyzer, just remove the automation and install a new one to get the latest version of the App Analyzer.
For client-managed installations, use the Monitoring apps. The Content Monitor app has a sheet for tracking deprecated charts. At reload, the Content Monitor app scans every app in the installation in order to list all applications and sheets that are using charts that are being deprecated. It also lists the installed extensions and their deprecation status. The Monitoring apps are bundled with the Qlik Analytics installation. The first version with the new sheet will be included in the May 2026 release. If you want to track usage in prior versions, the deprecated chart usage scanner will also be available on the product download page.
Thank you for choosing Qlik,
Qlik Support
We've made an update to Qlik Answers that delivers faster responses to your questions. See What's New in Qlik Cloud for the announcement.
The Data Analyst Agent in Qlik Answers now handles semantic search, expression building, and chart generation within a single, unified flow. When you ask a question, the Answers Agent and the Data Analyst Agent work together to deliver your response, and you'll see both reflected in the interface as Qlik Answers responds.
The practical effect: Qlik Answers can take your question, figure out what to search for, build the right expression, and generate the right visualization in a single connected process rather than as separate steps. Complex questions, the kind that involve comparisons across dimensions, multiple measures, or specific time periods, benefit the most because the agent can hold the full shape of your question in mind while deciding how to answer it.
Here's an example of how the same question flows through Qlik Answers. Previously, the response involved several specialized agents handing work back and forth. With the updated architecture, the question is resolved through a more direct flow, and you'll see the response come back faster.
Try it yourself! Ask any question you often repeat, especially one with comparisons or multiple parts. You'll notice Qlik Answers gets to the response faster.
You will see the difference the next time you open Qlik Answers, but everything else you rely on in Qlik Answers (your data, your spaces, your permissions, or the way you ask questions) will continue to work exactly as it did before the update went live.
We'll continue to evolve how the agents work as we add new capabilities, and we'll keep sharing what's changing along the way.
We'd love to hear how the updated experience feels in your day-to-day use. Reach out to your Qlik contact or share your thoughts in the community.
Thank you for choosing Qlik,
Qlik Support
来たる 6/10(水)、「AI Reality Tour Tokyo 2026」を開催いたします。
AI は急速に進化しています。その一方で、AI がもたらす価値でビジネス成果を実現している企業は、わずか 5% だという調査結果があります。最大の障壁となっているのは、AI モデルではありません。主な障壁は、データの品質・可用性・アクセス性・既存システムとの統合・ガバナンス・セキュリティなど、データやシステムであることが明らかになっています。先進的な企業では、あらゆる AI 戦略を最大化するために、単に最新のモデルを追求するだけでなく、「信頼できるデータ基盤」の構築に投資しています 。
AI がもたらす価値と現実とのギャップを解消するには?本イベントでは、AI を実現・加速・適応する最先端のソリューションをご紹介します。
Qlik のエキスパートによる基調講演、Qlik ユーザーの先進的な事例、Qlik 技術部門による最新の製品情報、Qlik のパートナー企業による最新のソリューションや展示ブースなどを予定しています。また、イベントの最後には、データのスペシャリスト同士の交流をお楽しみください。
お申し込みの締め切りは、6月 2日(火)17:00 までです。お早めにお申し込みください。
【開催概要】
日時:2026年 6月 10日(水)13:00 - 18:30(受付開始 12:00)
懇親会 18:30 - 19:30
会場:有明セントラルタワーホール&カンファレンス
東京都江東区有明3-7-18 有明セントラルタワー3F・4F
参加費:無料
お問い合わせ:Marketingjp@qlik.com までお問い合わせください。
The latest update to the App Analyzer brings a new feature: session-level data. Now, the App Analyzer can answer vital questions, such as which users are accessing which applications, how long they stay in each app, what sheets they use, the duration on each sheet, and the frequency of navigation between sheets. It also tracks the number of concurrent users within an app or across all apps in the tenant. The App Analyzer is released and updated by Master Principal Analytics Architect @Daniel_Pilla. He will monitor this thread should you have any questions.
In summary the App Analyzer’s key benefits include maintaining app size quotas, tracking user adoption, optimizing data models, and now analyzing user and session-level behavior.
The app analyzer can be easily programmatically installed along with all of the other monitoring apps via an out of the box Qlik Application Automation template. Please visit the links below for more information and to get started using it.

Identified significant stock imbalances across branches, where some locations consistently faced shortages while others held excess inventory. Uncovered opportunities for intra-branch stock transfers, reducing dependency on external procurement and improving fulfillment speed. Revealed demand patterns and seasonality trends using predictive analytics, enabling better stock planning and allocation. Highlighted inefficiencies in manual allocation processes, which were prone to delays and suboptimal decisions. Demonstrated how automation can streamline inventory workflows, reducing turnaround time and operational effort. Provided insights into high-demand and low-demand product categories, helping prioritize stock movement and optimize inventory levels. Enabled data-driven decision-making, improving accuracy in allocation and reducing stockouts and overstock situations.

Achieved improved inventory utilization by redistributing excess stock across branches, reducing overall wastage and idle inventory. Reduced stockouts and overstock situations, ensuring better product availability and balanced inventory levels. Enabled faster decision-making through real-time insights and automated recommendations, minimizing delays in stock allocation. Increased operational efficiency by automating manual workflows, reducing dependency on manual intervention and errors. Lowered procurement dependency by leveraging intra-branch transfers, leading to cost optimization. Improved supply chain responsiveness, ensuring timely fulfillment of demand across locations. Established a data-driven culture, empowering teams to make strategic decisions based on insights rather than assumptions

Supply Chain Managers – to monitor inventory levels and optimize stock distribution across branches. Inventory/Operations Teams – to manage stock allocation, identify shortages/surpluses, and execute intra-branch transfers efficiently. Business Analysts – to analyze demand patterns, generate insights, and support data-driven decision-making. Procurement Teams – to reduce unnecessary purchasing by leveraging existing inventory across locations. Leadership/Decision Makers – to track high-level KPIs and ensure operational efficiency across the supply chain.

Leveraging advanced analytics and AutoML transformed inventory planning by enabling predictive, data-driven decisions, reducing stockouts and improving operational efficiency.
The write table was introduced to Qlik Cloud Analytics last month so in this blog post, I will review how it works and how it can be added to an app. The write table looks like the straight table but editable columns can be added to it to update or add data. The updated/added data is visible by other users of the app provided they have the correct permissions. Read more on write table permissions here. Something else to note, if using a touch screen device, is you will have to disable touch screen mode for the write table to work. Looking at the write table for the first time, I found it intuitive and easy to use. Let’s create a write table with some editable columns to see how easy it is.
The write table object can be added to a sheet like any other visualization. Once it is added, columns can be added the same way dimensions and measures are added to a straight table. Below is a small write table with course information including the course ID, course name, instructor and location.
To add an editable column from the properties panel, click on the plus sign (+) and select Editable column.
The new editable column will be added. In the properties for the column, the title for the column can be modified and from the show content drop down, manual user input or single selection can be selected. Manual user input will create a free form column that the user can type into. The single selection option will allow me to create a drop-down list of options that the user can choose from.
I will change the title to Course Level and for show content I will select single selection and add three list items by typing the list item and then clicking on the plus sign to add it to the list. The list items will be displayed in the drop-down in the order they are added but can be rearranged by hovering over the list-item and dragging it to the desired position. List-items can also be deleted by hovering over it and clicking the delete icon that appears to the left.
When you come out of edit mode, the message below will appear for the editable column prompting you to define a set of primary keys.
Once you click Define, you will see the pop-up below where you can select the column(s) that will be used for the unique primary key. This is necessary to save and map the data entered in the editable column to the data model. I will select the CourseID column as the primary key.
Once this is done, I will see the Course Level column with the drop-down of list-items I added.
Let’s add one more editable column that takes manual user unput and name it Notes.
As I add data or update the editable columns, the cells will be flagged orange to indicate that my edits have not been saved. Once I save the table, they will be flagged green and any new values entered are visible to other users. A cell will be blue if another user is currently making changes to the row, thus locking it. Changes are saved for 90 days in a change store (temporary storage location) provided by Qlik. After 90 days, the data will be deleted. It is also important to note that if an editable column is deleted, the data will be lost. This is also the case if the primary key used for the editable column is removed.
It is possible to retrieve the changes from a change store via the change-stores API or an automation. Using the REST connection and the change-store API, the changes made in a write table can be retrieved and stored in a QVD (if needed for more than 90 days) or added to the data model for use in other analytics. Qlik Automate can also be used to retrieve data from the change-store using the List Current Changes From Change Store block or the List Change Store History block. From there the data can be stored permanently in an external system for later use or used in the automation for another process. Qlik Help offers steps for retrieving data from a change-store.
The write table can make it easy for users to add updates, feedback and important information that may not be available in the data model. Not only can this be done quickly, but it can be immediately visible to other colleagues. Learn more about the write table in the Product Innovation blog along with links to videos and write table FAQs.
Thanks,
Jennell
Hello Sitch users,
Starting April 30, 2026, all but three HubSpot Contact Lists API endpoints will be removed and return errors. Some Contact API endpoints will also be impacted. Details on affected endpoints can be found in Contact Lists API (v1) sunset moved to April 30, 2026 | hubspot.com.
To avoid any failures or data loss, all Qlik Stitch users are required to migrate their tasks to the latest HubSpot V4 version before April 30. All previous versions (v1, v2, v3) will no longer be supported.
If you have any questions, we're happy to assist. Reply to this blog post or take your queries to our Support Chat.
Thank you for choosing Qlik,
Qlik Support