A custom column after an aggregation prevents setting a filter at the dashbaod level

Get Help
1

I noticed a custom column after an aggregation in a question prevents setting a filter on this same question on a dashbaord level, is it a known behaviour?
Whereas when I do not add the custom column, a filter on a dashboard works perfectly fine.

It sounds like when adding a custom column after an aggregation the new base table to add a filter is the result of the aggregation rather than the initial table.

This behaviour is not convenient when we need a column for a sum and a custom column to divide this sum by a scalar to create a ratio.

Metabase Version: 0.43.2
Database : Redshift
Os: macOs Catalina
Browser: Google Chrome Version 106.0.5249.91
2

Hi @felici1b
There's an issue open about it:
https://github.com/metabase/metabase/issues/19744 - upvote by clicking :+1: on the first post
Depending on how your structure is, then you might be able to create a Custom Expression in the summarize metric section instead of adding it as a Custom Column.

1 Like