How to Avoid Information Overload and Context Switching in Qlik Cloud

Traditional dashboards often present a wealth of information on a single level. A user performing analysis must mentally switch between a global overview, a regional summary, and a detailed customer view. This constant context switching is inefficient and can lead to confusion.^[1] The goal of a modern dashboard is to guide the user through the data and deliver exactly the information they need at each moment of their analysis.^[2]

How the Intelligent Tab Container Works in Qlik Cloud

The Tab Container in Qlik Cloud is far more than just a tool for saving space. Combined with conditional «Show Conditions,» it becomes a powerful instrument for creating context-aware, guided analysis paths.^[3] Instead of displaying three separate charts, we create a single intelligent object that dynamically adapts its display to the user’s selection. For the complete properties reference, see the Qlik tab container documentation.

In this tutorial, you’ll learn how to create a Tab Container that automatically switches between a high-level territory view, a more detailed region view, and a specific customer drilldown view based on the user’s selection.

Understanding the GetSelectedCount() Function

The heart of our dynamic logic is the Qlik function GetSelectedCount(). Understanding this function is essential for creating any kind of conditional display. For a full breakdown of this function’s parameters and return values, see the GetSelectedCount() function reference.

What Does GetSelectedCount() Do?

As the name suggests, this function counts the number of currently selected (green) values in a specific field.^[4] It returns an integer.

• If no value is selected in a filter field called «Territory,» GetSelectedCount(Territory) returns 0.
• If the user selects exactly one territory (e.g., «North America»), GetSelectedCount(Territory) returns 1.
• If the user selects multiple territories, the function returns the corresponding count (e.g., 2, 3, etc.).

By checking whether the result is 0, 1, or greater than 1, we can precisely control which visualization is shown and when.^[5]

How to Create a Dynamic Customer Analysis in Qlik Cloud

In this hands-on section, we’ll build a Tab Container that displays three different analysis levels based on user selections.

The Goal: A Three-Level Analysis Path

1. Default view (no selection): A high-level view of «Revenue Risk of Churn by Territory.»
2. Territory drilldown (one territory selected): A more detailed view of «Customers by Avg Base Fee» within the selected territory.
3. Customer drilldown (one customer selected): An in-depth «Customer Drilldown» view for a single customer.

Prerequisites

Before you begin, make sure you’ve created three separate, working charts for the analysis levels described above. For optimal results and maintainability, these should be saved as master visualizations.^[6]

Step 1: Create and Populate the Tab Container

1. Drag a Tab Container object from the Extras panel (under «Dashboard bundle») onto your sheet.^[3]
2. In the properties panel on the right, under «Content,» click Add.
3. Add your three prepared master visualizations in the desired order:
   1. Revenue Risk of Churn by Territory
   2. Customers by Avg Base Fee
   3. Customer Drilldown

You now have a simple container with three tabs that you can switch between manually.

Step 2: Implement the Conditional Logic

Now we transform the static container into a dynamic tool by setting a «Show Condition» for each tab.^[7]

1. Configuring the Default View (Territory View)

• In the properties panel under «Content,» click on your first chart («Revenue Risk of Churn by Territory»).
• Find the Show condition input field.
• Enter the following expression:

  =GetSelectedCount(Territory)=0 and GetSelectedCount(AccountID)<>1 and GetSelectedCount(CustomerName)<>1

Logic breakdown: This view is only shown when NO territory (...=0) AND NOT EXACTLY ONE account (...<>1) AND NOT EXACTLY ONE customer name (...<>1) is selected. This is the perfect condition for a start or overview page.

2. Configuring the Territory Drilldown (State View)

• Select your second chart («Customers by Avg Base Fee»).
• In the Show condition field, enter this expression:

  =GetSelectedCount(Territory)=1 and GetSelectedCount(CustomerName)<>1

Logic breakdown: This view is shown when EXACTLY ONE territory is selected (...=1) AND the user hasn’t drilled down further to a single customer yet (...<>1). This is the logical second level of analysis.

3. Configuring the Customer Drilldown (Customer View)

• Select your third and final chart («Customer Drilldown»).
• In the Show condition field, enter this expression:

  =GetSelectedCount(CustomerName)=1 or GetSelectedCount(AccountID)=1

Logic breakdown: This most detailed view is shown when EITHER EXACTLY ONE customer name (...=1) OR EXACTLY ONE account ID (...=1) is selected. Using or makes the condition more flexible and robust.

Step 3: Hide the Tabs for a Seamless Experience

Result: Your container no longer displays tabs. Instead, the container’s content automatically switches whenever one of your defined conditions is met. You’ve created a dynamic, context-sensitive visualization!

Best Practices and Advanced Tips

• Use master items: Using master visualizations in containers is crucial. When you need to update a chart, do it once in the master item, and the change propagates everywhere.^[6]
• Keep it simple: Avoid too many nested conditions or too many levels. A good guided analysis has 2-4 clear stages. Too much complexity can confuse the user.^[8]
• Watch performance: A container with many complex, conditionally displayed charts can affect app load time. Make sure each individual chart in the container performs well on its own.^[9]
• Dynamic titles: Enhance the user experience by making the container title dynamic as well. You can use an expression like this to change the title based on the selection:

  =If(GetSelectedCount(Territory)=0, 'Churn Risk Overview', If(GetSelectedCount(Territory)=1, 'Avg Base Fee for ' & Only(Territory), 'Customer Details'))

Within your guided dashboard tabs, KPI objects in guided dashboards work perfectly as the first thing users see — presenting the most critical metrics before they explore details. For tabs that need multi-measure analysis, embed combo charts in interactive tabs to show relationships between different metrics in a single interactive view.

To persist tab state across sessions, combine your tab containers with dynamic bookmarks for tab state that automatically apply the user’s last selection.