Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Now accepting applications for the Qlik Luminary and Partner Ambassador Programs: Apply by July 6!
cancel
Showing results for 
Search instead for 
Did you mean: 
Pri_07_03
Partner - Contributor III
Partner - Contributor III

Best practice for chart-table interaction when Period chart uses snapshot month, but table shows monthly detail

Hi Experts,

 

I am facing a chart-table interaction issue in Qlik Sense.

 

My period chart uses snapshot logic:
H1 = September snapshot
H2 = March snapshot
Annual = latest month snapshot

 

But when user clicks H1, the detail table shows April to September records.

 

The issue is:
If April–September table contains judgment ×, but September snapshot does not contain ×, then selecting × from the table makes the H1 chart blank or inconsistent.

 

Example:
June = ×
September = ○

 

H1 chart uses September, so H1 = ○.
But table shows Apr–Sep and contains × from June.
When user selects × from table, chart cannot show it because H1 snapshot does not have ×.

 

This seems to be a granularity conflict:
Chart = period snapshot month
Table = monthly detail range

 

What is the best practice in Qlik Sense?

 

Should I:
1. Keep snapshot-based chart and prevent/ignore monthly judgment selections from affecting it?
2. Change H1/H2/Annual to range-based calculation?
3. Separate monthly analysis and period analysis into different sheets?

 

I want to avoid confusing behavior for users and explain the correct design to the client.

 

Please suggest the recommended approach.

2 Replies
william12342344
Contributor III
Contributor III

Best practice is to separate snapshot and monthly analysis.

Your H1 KPI is a September snapshot, so it should only use September data. The table is a monthly history (Apr–Sep), so it has a different grain.

Recommended:

  • Keep H1/H2/Annual as snapshot calculations.
  • Prevent monthly detail selections from changing snapshot KPIs (use set analysis or separate fields).
  • Put monthly trend/detail analysis on a separate sheet if possible.

Do not change H1 into a range calculation unless the business definition changes from “status at snapshot date” to “status during the period.” Otherwise users will see confusing results.

jasonmiller11tt234
Contributor II
Contributor II

This is a granularity mismatch. I'd keep the snapshot chart as-is and separate it from monthly analysis (or use alternate states/set analysis). Mixing snapshot and range-based selections usually creates confusing results for users.