Inconsistency between Period-based chart and Month-based detail table
Hi,
I am working on a Qlik Sense dashboard where different visualizations are built using two different data granularity levels (Month-level and Period-level), based on client requirements.
Currently, I am facing an issue where the bar chart becomes blank when a specific judgment value is selected from the straight table, and I would like to understand the best approach to handle this scenario.
1. Month Sheet (Detailed Data) Contains:
Year Month Product Judgment (〇, △, ×, ★)
2. Period Sheet (Aggregated Data) Contains pre-calculated judgments:
Current Implementation Bar Chart (Built on Period Sheet) Logic used:
H1 → Uses Month = 9 from Period sheet H2 → Uses Month = 3 from Period sheet Annual → Uses latest month from Period sheet Recent 3 Months → Uses latest month from Period sheet
Straight Table (Built on Month Sheet)
Displays detailed monthly data A bridge table (AxisKey ↔ YMKey_Bridge) is used
Example:
When user clicks 2024 H1, the table shows: April to September (Month 4–9)
Issue Description Scenario:
In Period sheet (Month 9 for 2024 H1) → Judgment = 〇 or △ In Month sheet (Apr–Sep 2024) → Some months (e.g., June, July) have ×
Problem:
User selects 2024 H1 Table shows April–September data correctly Then user clicks × (from table) Bar chart becomes blank
Root Cause (as per my understanding):
Chart uses Period-level judgments Table uses Month-level judgments The selected value × does not exist in Period sheet for that H1 Hence chart has no matching data
Client Requirement The client wants: Even after selecting a judgment (e.g., ×) from the table, the bar chart should still display data, following the existing period logic.
Question What would be the best approach to handle this scenario?
Constraint
The current period logic must remain unchanged (as it is client-defined) Prefer a solution that does not break existing working functionality
Any suggestions or best practices would be greatly appreciated. Thank you in advance!
This issue is happening because the chart and table are working at different data granularities.
The H1 chart is based on the September, because September represents the official H1 result.
However, when the user clicks H1, the table shows monthly detail records from April to September.
Because of this, a judgment selected from the table may exist in one of the detail months, but it may not exist in the September snapshot used by the chart.
For example:
H1 chart is calculated from September only
Table shows April to September
If × exists in June but not in September:
Table can show/filter ×
But H1 chart will not change, because the chart does not use June data
So this is not a Qlik technical issue only.
It is mainly a business logic conflict between snapshot-based reporting and range-based drill-down reporting.
If the requirement is that the chart must always react to table selections, then H1 should not be calculated from September only.
Instead, H1 should be calculated from all Apr–Sep records.
In this approach:
H1 chart uses Apr–Sep data
If user selects ×, the chart also updates
Chart and table remain consistent
But this means the H1 value may no longer match the official September from the Period sheet.
If the requirement is that the chart must always react to table selections, then H1 should not be calculated from September only.
Instead, H1 should be calculated from all Apr–Sep records.
In this approach:
H1 chart uses Apr–Sep data
If user selects ×, the chart also updates
Chart and table remain consistent
But this means the H1 value may no longer match the official September snapshot from the Period sheet.
