Filtering in measures or filtering on a report - which is best practice

[lottieritchie]

Hi, 

I'm just wondering which is best practice, to either build filters into my measures, or to use the filters on reports. 

I have, as an example, a measure telling me the total number of outstanding tickets our team needs to answer. 

I also want to see this information by priority. 

Example: 30 outstanding tickets; 15 High priority, 10 Medium priority, 5 Low priority. 

Should I build a new measure for each priority, or should I use the filters on the report page to filter my total outstanding tickets measure? 

Just wondering which is best practice as I know both work. 

Many thanks for your help. 

[amitchandak · Accepted solution]

@lottieritchie , it depends on need. You have the option to use visual level filter.

but if you want them in the same visual, then you need separate measures. Please use filter and create separate measure

[timg · Accepted solution]

Hi,

This kinda depends on the reporting requirements. If a measure should always only show the high priority tickets, it may be best to hard code the filter into a measure, so that end-users can't accidentally change the filter. However, if your report users can receive extra value from the report by being able to compare how many tickets there are per category, you may be better off choosing a slicer or report filter. 

hope it helps!

regards,

Tim

[amitchandak · Accepted solution]

@lottieritchie , it depends on need. You have the option to use visual level filter.

but if you want them in the same visual, then you need separate measures. Please use filter and create separate measure