In this blog post, I will cover three new features in Qlik Cloud:
Subtotals in the straight table
Exit error
Creating text and image objects from pasted images
These are small features, but useful improvements that can be used when building your analytics apps.
Subtotals in the Straight Table
The first is the ability to add a subtotal row to a straight table. This is something we are used to seeing in a pivot table but not a straight table. Developers can now toggle on Show subtotals in a dimension field of their straight table to add subtotal rows.
Once Show subtotals is toggled on, the Label property becomes available allowing the developer to rename the label. In the table, a subtotal row is added for each asset class.
Exit Error
The second new feature is Exit Error, which is used in the script to end the execution of the script with a user defined error message. The syntax as found in Qlik Help looks like this:
Exit Error expression [(when | unless condition)]
For example, assume you are loading data in a table, and you want to exit the script execution if no data has been loaded. Using Exit Error, a variable can be checked (or some other condition) to determine if there are rows in a table that was previously loaded. If there are, continue with the script; if not, exit the script with a message. In this example, the vOpenOrders variable will be 0 if there are no rows in the table.
If the variable vOpenOrders is equal to 0, then exit the script and show the message “No open orders were loaded.” This is how the error will appear.
Creating Text and Image Objects from Pasted Images
The last new feature is a cool shortcut to create a text object or an image object. Simply paste text or an image onto an empty area on a sheet and a new text object or image object will be created. In the case of images, the pasted image will be automatically saved to the media library – a time saver. On the sheet below, I pasted this text: “I am going to create an image with this text.” and this image:
And a text object and image object were created without any additional work from me.
Note that the developer will need upload permissions for the image to be added to the media library.
That's three new ways Qlik Cloud is making app development easier — smarter subtotals, cleaner error handling, and a slick shortcut for pasted content. Small features, big time savings. Try them out in your next app and stay tuned for more updates coming soon.
Thanks,
Jennell
...View More
The 2026 World Cup kicks off today!
A few weeks ago, I published a post on how we built Choose Your Champion 2026, a World Cup bracket app powered by Qlik. That post went into the technical details: the data model, the ML experiment in Qlik Predict, the React front end. If you haven't read it, start there.
So far, 90+ brackets have been submitted. One of them wasn't filled out by a person at all. It was generated by the machine learning model we trained with Qlik Predict, using FIFA rankings, player ratings, and head-to-head history. The model has Spain winning it all!
Here's mine, and here's Qlik Predict's.
If you haven't filled one out yet, do it here. Once you're in, use the Compare button on the leaderboard to see where your picks differ from mine, or from the model's. Brackets get scored automatically as matches are played, so the leaderboard will keep moving all the way to the final on July 19.
We also opened up a Choose Your Champion space on Qlik Community. That's where we'll be posting leaderboard updates during the tournament, and where you can share your bracket, ask questions about the app, or make your case for why the model got it wrong.
If you're interested in the broader question of when models beat human intuition (and when they don't), take a look at Model vs. Mastery.
Enjoy the tournament!!
...View More
Our Data Products Storylane has been given a revamp!
TAKE THE TOUR
Data Products are highly trusted, re-usable, and consumable data assets. Data elements such as raw data, transformations, data quality rules, contracts, access patterns, and infrastructure have been organized into a single cohesive unit to align with specific requirements and objectives of a business to create a Data Product.
Data Products come with the Qlik Trust Score, a score given to data products based on seven factors, Validity, Completeness, Discoverability, Usage, Timeliness, Accuracy, and Diversity. The Qlik Trust Score ™ gives you confidence in the quality and health of your Data Products so you can be empowered when using them throughout your business. You can also view the Data Product Lineage, which is a flow chart that shows you the origin of the Data Product, so you can track it down to its source. Available Data Products can be found in the Data Marketplace, a collection of Data Products that are ready for use.
If you want to learn even more about Data Products, Datasets, Data Quality and Data Validation Rules check out Mike Tarallo's video series here:Data Products for Qlik Analytics
...View More
A table recipe is an easy, no-code way to prepare a data set for an app, data flow, script or ML experiment. It is a great way for new users to prepare their data and get started building an app without having to write the script to transform the data. It can also be used by experienced users for quick data prep. Table recipe is available in Qlik Cloud Analytics from the Analytics activity center > Prepare data. You can also access it from the + Create menu option or + Create New button in the catalog. To begin using it, open table recipe, give it a name and select the space you would like to create it in. Once that is done, you will be prompted to select the data set. Note - the table recipe processes one data set at a time.
Once a data file is selected, you can view the fields to confirm it is the correct data set and then you can load it into table recipe. Once it is loaded, you will see a pop up indicating the number of rows and columns in the dataset. Note that all the rows may not be loaded into the table recipe editor, but the recipe will be applied to the entire data set when it is run. Below is a look at the table recipe. On the left is the functions panel that includes several functions that can be used to prepare the data. Functions are grouped as general, columns, strings, dates, numbers and math. On the right is where the steps in our recipe will be added.
Let’s begin with a simple step like deleting a column. I have a Fax column that I do not need so to delete the column; I can click on the column menu (three vertical dots) and select Delete column.
The step will appear on the right in the table recipe, and I can click Apply to remove the Fax column.
Next, let’s split a column into two new columns. I have a Contact Name field with the contact’s full name. I would like to split the name into two fields – one for first name and one for last name. To do this, I will select the Split column function from the list of string functions on the left. Then I can update the details and apply the step. I will change the separator to a space since that is what separates the first and last name in the ContactName column.
Once I apply that step, I can see the two new fields it generated.
I will open the column menu and select Rename column to change the names of the new columns. Once I apply those steps, the columns and the recipe look like the image below. Keep in mind that the table recipe has steps that flow in a specific order. If those steps were to change, you may not get the expected results. For example, if I moved the rename column step above the split column step it would not work because the column I am renaming does not exist yet.
It is also easy to reorder the columns with the table recipe. The Reorder column function is found in the function group named Columns. Simply, select the column you would like to move and click on the Reorder column function. To move the Address column to the left of the City column, I will select the City column from the Anchor column drop down and then click Apply.
We are also able to apply filters to the data if we want to focus on specific rows. In this example, Country has two different values for the United States – USA and US. I would like to change the US values to USA.
After applying the filter, I can see that I have 6 rows with US as the Country. I can use the string Search and replace function to replace US with USA.
This step included my filter, so it only applied it to the rows I have filtered on.
Let’s perform one more step that I use all the time when loading data. We will extract date parts from the OrderDate field. This will allow us to create other date fields such as month and year fields. If I select the OrderDate field and then select the date function Extract date parts, I am presented with all the possible date part fields I can add as a column to my data set. I simply can toggle on any new fields I would like to add.
Once this step is applied, I can see the 4 new date fields I added.
When all the steps have been added to the table recipe, the next steps are to set the target and run the recipe. Setting the target is nothing more than giving the target file a name and file type (qvd, parquet, txt or csv) and selecting the space to create it in.
What is nice about the table recipe is the steps are applied and stored in a new file, separate from the original data set, so you do not have to worry about incorrectly modifying the data set. Once the target is set, the Incomplete recipe message at the top of the page will change to Valid recipe and the Run recipe button will be enabled. Once the recipe is run, you can view your new data set and use it accordingly. The target data set will be stored in the desired space and can be accessed anytime via the catalog.
Notice how all these steps we are creating are very easy and intuitive to build. You do not have to be an expert to perform these steps, and the editor is very user friendly and has a clean flow. What is also nice is that you can see that each step is working as expected when you apply it. Take this product tour to get a feel for the table recipe and then try it for yourself. To learn more, check out Qlik Help.
Thanks,
Jennell
...View More
Hey guys join @Jennell_Yorkmanand I for a quick community resource update as we highlight some of the latest ideas, enhancements, and best practices being shared across the Qlik Design Blog and Qlik Community.
From dashboard design and developer capabilities to visualization techniques and platform improvements, this session is a fast-paced roundup of useful content and community-driven insights to help you get more out of Qlik. Whether you’re building apps, designing dashboards, or exploring new capabilities, this is a great way to stay connected with what’s happening across the Qlik ecosystem.
Register here LinkedIn Live
...View More
Today I want to introduce you to a gem that you may be missing out on. It is the Do More with Qlik community forum lead by @Michael_Tarallo. This forum is made up of concise videos that cover everything from Qlik capabilities to innovative ways to solve business challenges. It is for users of all levels, beginners to seasoned Qlik users, with a wide range of topics. Check out this introductory video to learn more and bookmark the forum. You do not want to miss out on this!
Thanks,
Jennell
...View More
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.
What's in the app:
Choose Your Champion is broken into 4 parts:
Build a bracket: Pick your group stage winners, advance teams through the knockout rounds, and lock in your champion.
Check the predictions: For every possible matchup in the tournament, the app surfaces a Qlik Predict generated win probability for each team plus a draw probability. When you're unsure about a matchup, you can pull up the prediction and use it to decide which team advances.
Explore historical World Cup data: The app includes various visualizations to help you uncover insights from past tournaments: goals, top scorers, host nation performance, biggest upsets. All powered by the associative engine.
Leaderboard: As real matches get played in June and July, submitted brackets are scored automatically and players are ranked in the leaderboard table.
Under the hood: how the predictions work
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:
Elo ratings for both teams
FIFA rankings and points snapshot to the match date
Rolling 10-match form per team: win rate, goals for, goals against, goal difference
Head-to-head history in the last 10 meetings
Context flags: neutral venue, tournament tier, cross-confederation
World Cup pedigree: a score rewarding teams for deep runs in past tournaments, with more recent success weighted heavier
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:
elo_diff
rank_diff
is_neutral
h2h_team_a_advantageetc...
A few other calls that mattered:
Filtering to competitive matches only. A friendly between a top side's B squad and a mid-tier opponent tells you almost nothing about what happens in a World Cup group stage game.
Exponential decay on World Cup pedigree. A deep run in 1970 still counts, but less than one in 2022.
Removing rows with too many missing features. FIFA rankings don't go back to the 90s for every team, so some rows had to get dropped.
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
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.
A few takeaways
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!
Go fill out your bracket
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!
...View More
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'sDennis Jaskowiak andEkaterina 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 (QVF)here.
Thanks,
Jennell
...View More
