Why can’t we filter a dashboard when we are utilizing double aggregation?
Apparently when we use this type of aggregation, the filter is directed after the first aggregation, limiting the filter fields.
@flamber Ok, now I understood. I have to first aggregate with all the fields that I want to filter, and then aggregate again to show that in the graphic. I though that I could filter everything before the first grouping was made.
@beey It’s only the last “layer” that is being sent in the metadata. This is also only of the blockers from being able to do other interesting things.
We have an issue open about getting more detailed information, so we are able to do more advanced parsing: https://github.com/metabase/metabase/issues/5594 - upvote by clicking on the first post
There are other issues too, but can’t remember the exact ones.
I have question on this topic. I understood only the last "layer" is being sent in the metadata. But there are cases where you want to filter on the previous layer (first aggregation), and you do not want to group by that value on the second layer.
Example : I want the average revenue by month.
First layer : Metric : Revenue Group by : Month
Second Layer : Metric : Average(Revenue)
Now i want the average revenue by month for a customer. I should then filter the results of the first layer, but i cannot access it anymore right from a dashboard ?
@tpatulacci There's a lot of security involved here too. Example, let's say it's Paycheck instead of Revenue, and someone who might have permissions to view the question, but edit it, they should not be able to create a filter, where they can get information at person-level.
It's complicated and complex. We're trying to not over-complicate the GUI, but it has some disadvantages too.