Calculated column slicer and parameter adjustments dilemma

Thanks for the reply Ibendlin.

I think I created a measure yesterday that works. Although, so slow that after waiting several minutes without the table visual finishing, it seems the approach is not a usable one.

The measure uses a sumx-statement with the above mentioned slicer values as filters, acting on millions of rows of data. I am thinking perhaps using variables and / or a leading filter in the DAX-statement could speed things up.

Perhaps I need to leave this implementation be.

Hi 1up, hello lbendlin, thank you for your prompt reply! 

I agree with your perspective.

It is essential to filter as much data as possible before executing logical tests.

You could use the Performance Analyzer in power bi desktop to check the time reduction before and after: 

Here are two more articles on performance tuning dax for your reference:

Performance Tuning DAX - Part 1 - Microsoft Fabric Community

Performance Tuning DAX - Part 2 - Microsoft Fabric Community

Best regards,

Joyce

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