Use implicit measure as page-level-filter in Power BI

[AndyHermle]

Dear Experts: 

I asked the Microsoft Co-pilot if it is possible to use an implicit measure as a page-level-filter.

The answer that came up is definitely not correct since I tried it out and YES it is possible to use implicit measures as page-level-filters.  

Microsoft Co-Pilot:

In Power BI, implicit measures (like sums, averages, etc., automatically created by Power BI) cannot be directly used as page-level filters. However, you can achieve similar functionality with some workarounds:

1. Create a calculated column: Instead of relying on an implicit measure, create a calculated column that performs the same calculation. You can then use this column as a page-level filter.
2. Use a disconnected table: Create a disconnected table with the values you want to filter by and use DAX to create a measure that references this table. This can help simulate the effect of a page-level filter
   
3. Apply visual-level filters: Apply the implicit measure as a visual-level filter on each visual on the page. While this approach is more time-consuming, it achieves a similar result

[Anonymous · Accepted solution]

Thanks for the reply from amitchandak , please allow me to provide another insight:

Hi, @AndyHermle 
Thanks for reaching out to the Microsoft fabric community forum.

Yes, as amitchandak mentioned, we typically use fields in page-level and report-level filters, while measures can currently only be used in visual-level filters.

The implicit measures you referred to are automatic aggregations placed in visuals, which are different from the fields used in page-level and report-level filters. Implicit measures are mostly involved in calculation groups. Below is a screenshot of the relevant documentation:

For more details, please refer to:

Create calculation groups in Power BI - Power BI | Microsoft Learn

Moreover, we can deduce from the phenomenon that even with calculation groups enabled, we can still use page filters, which proves that what is used in page filters is not implicit measures.

Of course, if I misunderstood your point, please feel free to correct me. We look forward to your feedback.

Best Regards,

Leroy Lu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[AndyHermle]

Dear Linyulu, 

thank you very much for your detailed explanation. Great, this clears it up for me. Thank you for the superb insights. I now fully understand this matter. 

Thank you again and have a nice day. 

Best Regards, Andreas

[Anonymous]

Hi， @AndyHermle 
We are very pleased to hear that the issue has been resolved. Thank you for sharing the solution with us. If you are willing, you might consider accepting this solution, as it can also help other community members facing the same issue find a solution more quickly.

Of course, if there is anything else we can do for you, please do not hesitate to contact us. Once again, thank you for your contribution, and we look forward to your response.

Best Regards,

Leroy Lu

[Anonymous · Accepted solution]

Thanks for the reply from amitchandak , please allow me to provide another insight:

Hi, @AndyHermle 
Thanks for reaching out to the Microsoft fabric community forum.

Yes, as amitchandak mentioned, we typically use fields in page-level and report-level filters, while measures can currently only be used in visual-level filters.

The implicit measures you referred to are automatic aggregations placed in visuals, which are different from the fields used in page-level and report-level filters. Implicit measures are mostly involved in calculation groups. Below is a screenshot of the relevant documentation:

For more details, please refer to:

Create calculation groups in Power BI - Power BI | Microsoft Learn

Moreover, we can deduce from the phenomenon that even with calculation groups enabled, we can still use page filters, which proves that what is used in page filters is not implicit measures.

Of course, if I misunderstood your point, please feel free to correct me. We look forward to your feedback.

Best Regards,

Leroy Lu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[AndyHermle · Accepted solution]

Dear linyulu and amitchandak, 

thank you very much for your expert help. As you can see on this screenshot, I definitly used an implicit measure as page-level-filter. The implicit measure is Sales Amount. Or am I getting something wrong here?

Your valuable help is very much appreciated. Thank you very much in advance.

Best Regards, Andreas

[Anonymous]

Hi, @AndyHermle 
Thank you for your prompt response.

I believe there is a difference in our understanding of implicit measures. From the examples I provided below, you can see that the same field is referenced. It is evident that in the visual-level filters, the format "xx of yy" (where xx is the aggregation method and yy is the field name) represents implicit measures. However, in the page-level filters, it only contains yy (the field name), which is not an implicit measure.

This aligns with the definition in the official documentation:

For more details, please refer to:

https://learn.microsoft.com/en-us/dax/dax-glossary#implicit-measure

I hope my explanation helps you understand implicit measures.

Best Regards,

Leroy Lu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[amitchandak]

@AndyHermle , Can you share how did you use implicit measure in Page level filter. We can use a column in page level filter and that will not have any aggegation associated with. As far as I know we can use measures in visual level filters. 

Please share example or screenshot to better understand it.