Best practice for indicating column in table that don't respect filters?
We have a table that displays exam results.
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.
Re: Best practice for indicating column in table that don't respect filters?
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.