Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
jasonladicos
Partner - Contributor II
Partner - Contributor II

Best practice for indicating column in table that don't respect filters?

We have a table that displays exam results. 

Exam nameExam dateMeanDifficulty scoreN
Midterm1/1/202077.60%.7622
Final4/30/202077.32%.6833

 

The difficulty score is pre-calculated and applies to the overall exam results.

If someone filters the sheet by learner, then the Mean and N will change  accordingly, but the difficulty will not change because it is calculated for the entire cohort.

Someone could also filter for a particular question on an exam, or a "topic tag" that is attached to questions on the exam. In these cases, the Mean might change, but in this case the N would stay the same, and again, the difficulty would stay the same, because it's not calculated by question, or by topic.

There are a number of additional ways that someone might also filter the data, so while I've considered hiding and showing the column based on GetCurrentSelections(), that seems like it could get out of hand pretty quickly.

Does anyone have a best practice for indicating fields that are pre-calculated and aren't going to respect filters?

We've been considering using asterisks and/or footnotes to orient people who are reviewing the data, but I'm wondering if there is something else I'm not considering.

4 Replies
Lisa_P
Employee
Employee

Possibly indicate this in the column title eg Global Difficulty Score or Overall Difficulty Score

albertovarela
Partner - Specialist
Partner - Specialist

One consistent way to maintain and display information about the dimensions and measures is by adding a description to the master items then turning on the details on the charts. That will enable the show details when hover over a chart.  

I hope this helps.

 

Capture.PNG

 

 

jasonladicos
Partner - Contributor II
Partner - Contributor II
Author

Thank you for the insight - we haven't really given much thought into that level of documentation, so something to ponder, for sure.

jasonladicos
Partner - Contributor II
Partner - Contributor II
Author

Thank you for the suggestion - naming is hard!

I'll have to think about a way that we might be able to use naming (possibly in conjunction with the documentation trick described below) to communicate content and limitations.