Forum Discussion
Simple Drill Down
You clearly have hierarchies here, so you have to create them. Bear in mind that hierarchies must reside in one and the same table. When designing tables with hierarchies, think about what a Date table looks like... Once you get your hierarchy/hierarchies right, you're almost done with your task.
Here's a file that does what you want:
https://1drv.ms/u/s!ApyQEauTSLtOgZlNkcwZPyDsKLJojw?e=iWH3bv
Anonymous
I don't really understand what you mean. If you select just the right entities from your tables, the average will return the raw score since it won't have to average over many items. But this is a measure, so it has to work for any context. Hence the aggregation. An average makes sense. Other aggregations not so much. If you want to check if there is just one entity in the context, then you'll have to deal with detecting context. You can use functions such as HASONEVALUE, ISINSCOPE, HASONEFILTER... But such a measure will not be universal.
understood. thanks again!