Dashboard filter on query with two summary steps

I’m fairly sure what I try seems to be impossible.
I’m using Dashboard filters often. But I have a query where I calculate cumulative sum of a distinct count of a specific field in a result set grouped by date (weeks). This is done with a two stage summary.

This is possible to put in a Metabase query, but if I add a filter to this query from a dashboard, then the filter is applied on the first result set - so after the first summary - instead of on the initial query data. Which means the filter is not working.

Is there someone who knows how to resolve this? Could it be added to the Metabase features?

1 Like

Hi @neeohw
Not sure what you’re asking for, but it sounds like this - upvote by clicking :+1: on the first post of each issue:
https://github.com/metabase/metabase/issues/6583
https://github.com/metabase/metabase/issues/5346

Hi @flamber,

Nope, both issues are not what I’m asking for.

Let’s say I have a table with transactions. The records have four columns: from, to, transaction, timestamp.
Users can have multiple transactions. But I would like to have a count of the distinct number of “from”-values per week so I can see how many users actually did a transaction. That’s the first grouping. Then I group again to have the cumulative count of distinct “from”-values. Again per week.
This is perfectly possible in the query view.
But let’s say I use this query as a basis for a dashboard and now I would like to filter the “to”-column with a dashboard filter, so I can have the same query run for a specific destination of transactions.
This is currently not possible, because the filter is automatically applied on the result of the first grouping instead of on the initial data…

Your github-issues do not mention this problem, so I don’t really see why they’re relevant.

@neeohw I still don’t understand, so perhaps some screenshots or examples of how you’re doing what you want in Query Browser.
It sounds like you almost want the functionality from QB on the dashboard.

Hi @neeohw! I'm having the exact same issue. Did you discover a solution by any chance?

@snabar If you try to provide more details (and screenshots), then perhaps it would be possible for me to fully understand what problem is.