Hi @Ummehaani, per_filter in window function only provide flexibility of the calculation being impacted by all filters or no filters in the visual (except top/bottom N filters, according to the order of evaluation of QS).
For your question, I aggree with @darcoli that having the ifelse() function nested in the LAA function is the solution. And you can link the condition with a parameter (such as ifelse(Group_label=${parameterGroup}…) to use the parameter control to trigger the filter.
We currently have the limitation of using only single select parameter in calculated field, so you have to filter on the group one by one to see the result. Good news is that we are working on the IN/NOTIN calculation function to consume multi-select parameters. When that feature is enabled, you will be able to link a multi-value parameter to filter on the result while not being impacted by the visual filter.
3 Likes