Qlik Sense Combo Chart: Bar + Line [Step-by-Step]

What Is the Combo Chart in Qlik Sense and When Should You Use It?

Why Does Your CFO Need Revenue and Margin on the Same Chart?

Revenue goes up. Margin goes down. You need both on the same chart to see the disconnect. That is what a combo chart is for.

Combo charts exist because the most important business questions involve two measures that move in opposite directions. Revenue vs margin. Headcount vs productivity. Sales volume vs average deal size. If you are only showing one measure per chart, you are hiding the relationship that matters. A finance director at a distribution company once had three separate charts on the same dashboard: rising revenue, flat headcount, declining margin. Nobody connected them. One combo chart made the problem visible in under 30 seconds. The company had been growing into lower-margin product lines for 18 months without anyone seeing it at a glance.

The Qlik Cloud combo chart solves this by combining a bar chart and a line chart in a single visualization.^[2] It uses two separate Y-axes, so large-scale absolute values (like revenue) sit on the primary axis and small-scale relative values (like percentages) sit on the secondary axis.^[3] For how to pick the right chart type before you start building, the Data Modeling Course covers visualization selection as part of the broader dashboard design approach.

When Should You Use a Combo Chart in Qlik Sense?

The combo chart is a specialized tool. Use it for the right job and it is one of the most powerful charts in Qlik. Use it for the wrong one and it creates more confusion than clarity.

✅ Use a combo chart for:

• Comparing volume and rates: This is the classic use case. Combine absolute numbers (bars) with percentages or rates (lines) to reveal their relationship. Examples: revenue vs. margin %, website traffic vs. conversion rate.^[4]
• Illustrating cause-and-effect hypotheses: Visualize how one measure might influence another. Example: marketing spend (bars) vs. new leads generated (line).
• Comparing measures with vastly different scales: Any two measures that share a common dimension (like time) but have incompatible scales are perfect candidates.^[1]

❌ Avoid a combo chart for:

• Simple category comparisons: If you only want to compare revenue across regions, bar charts for individual measures are clearer and more effective.^[5]
• Pure trend analysis: To compare trends of multiple measures with similar scales (e.g., revenue for three different products over time), a line chart is the better choice.^[5]
• Multi-dimensional analysis: The combo chart in Qlik Cloud supports only one dimension. For analyses requiring two or more dimensions, use a pivot table or scatter chart.^[1]

What Is the Dual-Axis Dilemma in Qlik Sense Combo Charts?

What Are the Three Big Pitfalls of Dual-Axis Charts?

1. Creating false correlations (spurious correlations): The point where two lines intersect in a dual-axis chart immediately draws attention. But that intersection is often a mathematical coincidence produced by the chosen axis scales, with no real significance.^[8] Focusing on it can lead to completely wrong conclusions.
2. Distorting data through arbitrary scales: The visual relationship between two data series can be manipulated simply by changing the min/max values of the Y-axes. You can make a small change look dramatic or a large change look trivial — whether intentionally or not.^{[6], [9]}
3. Causing cognitive overload: A chart with two axes, multiple colors, and different chart types demands significant mental effort from the viewer just to figure out which line belongs to which axis. This increases the risk of misinterpretation.^[8]

How Do You Use Dual Axes Responsibly in Qlik?

• Use different visualization types: Combine bars (for the primary axis) and a line (for the secondary axis). This creates a much clearer distinction than using two lines.^[10]
• Color-code your axes: In the styling panel, match the axis title, labels, and the corresponding data series (bars or line) to the same color. This gives the viewer an immediate visual cue.
• Label everything clearly: Label both Y-axes with the measure name and unit (e.g., “Revenue in EUR”, “Margin in %”).
• Start axes at zero (where possible): For absolute values like revenue, starting the axis at zero prevents distortion of proportions.

How Do I Create a Combo Chart in Qlik Cloud?

How Do I Build My First Combo Chart in Qlik Sense in 5 Minutes?

1. Add the object: In sheet edit mode, drag a “Combo chart” from the assets panel onto your sheet.^[11]
2. Add a dimension: In the properties panel on the right, click Data > Dimensions, then “Add dimension”. Select a field for your X-axis — typically a date field like OrderDate.
3. Add the primary measure (bars): Under Data > Measures, in the “Bar length” section, click “Add” and select your primary measure, e.g. Sum(Sales). This is assigned to the left Y-axis.
4. Add the secondary measure (line): In the same area, under “Line height”, click “Add” and select your secondary measure, e.g. Avg(Margin).
5. Assign to the secondary axis: Click your new line measure to expand its properties. Under “Axis”, change the selection from “Primary” to “Secondary”.^[12]

You now have a working combo chart with two distinct axes that correctly visualizes your data. For a full property reference, see the Qlik official combo chart documentation.

What Does the Properties Panel Look Like in Qlik Sense Combo Charts?

Mastering the properties panel is the key to building professional, insightful charts. Here is a breakdown based on the Qlik Cloud UI.

How Do You Intelligently Combine Multiple Measures in Qlik Sense Combo Charts?

How Do I Analyze Market Share vs. Competition in Qlik Sense Combo Charts?

Business question: “Are we growing faster than the overall market, and how is our market share developing?”

For the cleanest results, combine expression optimization for chart calculations with the multi-measure patterns below. Set analysis for chart expressions lets you compare your company’s figures against market totals in a single formula.

Qlik expressions using Set Analysis:

• Our revenue: Sum({<Company={'Our Company'}>} Sales)
  Explanation: The Set Analysis modifier {<...>} tells Qlik to calculate only the data for “Our Company”, regardless of the current selection.^{[18], [19]}
• Market share in %: Sum({<Company={'Our Company'}>} Sales) / Sum({1} Sales)
  Explanation: The numerator is our revenue. The denominator, Sum({1} Sales), totals revenue across all companies in the data model — the {1} identifier ignores any user selection.^{[20], [19]}

How to read it: A strategist can immediately see whether absolute revenue growth (rising bars) is also translating into market share gains (rising line). A stagnating market share alongside growing revenue signals that you are only keeping pace with the market — not taking share from competitors.

How Does Conditional Coloring by Formula Work in Qlik Sense?

Color bars dynamically — for example, red when actual spending exceeds budget, green when it comes in under.

How Do I Ensure Quality and Troubleshoot Qlik Sense Combo Charts?

What Does a Perfect Combo Chart in Qlik Sense Look Like?

For community-tested design approaches, the combo chart design tips on Qlik Community are worth reviewing before finalizing your chart.

• [ ] Clear message: Does the title communicate a clear business insight?
• [ ] Less is more: Are you using a maximum of 3-4 measures to avoid visual overload?^[17]
• [ ] Correct axes: Are absolute values on the primary axis and relative values on the secondary axis?
• [ ] Logical chart types: Are you using bars for volume and line charts for trend components?
• [ ] KPI context: Pair your combo chart with a gauge chart for KPI context — showing where a metric falls within defined performance ranges.
• [ ] Business framing: Does the chart title state the business question, not just the measure names? A finance dashboard that shows “Revenue growing while margin contracts” communicates more than one titled “Revenue + Margin by Month.” See how chart selection drives outcomes in the Finance Dashboard guide.
• [ ] Clear labeling: Are both Y-axes clearly labeled with the measure name and unit?
• [ ] Performance: For large datasets, have you added a calculation condition to keep load time under 3 seconds?
• [ ] Context: Are relevant reference lines (e.g., for targets) in place?

What Are Common Problems and Solutions in Qlik Sense Combo Charts?

• Problem: “My line is flat / barely visible at the bottom of the chart.”
  Solution: The measure for the line is assigned to the primary Y-axis. In the measure properties, change “Axis” from “Primary” to “Secondary”.
• Problem: “My chart is cluttered with too many bars and lines.”
  Solution: Reduce the number of measures. Lean into Qlik’s interactivity: instead of showing 5 product lines as 5 separate lines, create one chart and a separate filter pane for the product lines.
• Problem: “The chart loads very slowly.”
  Solution: Implement a Calculation condition under Add-ons > Data handling. An expression like Count(distinct Month) <= 24 ensures the chart only calculates once the user has narrowed down the time range.
• Problem: “The labels on the X-axis are overlapping.”
  Solution: Navigate to Appearance > X-axis. Change “Label orientation” to “Tilted”. If that is not enough, the dataset is too granular — consider aggregating to a higher level (e.g., from day to week).