Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Hi all.
Can anybody suggest why my solution works so poorly in terms of speed?
1) I am building a scatter chart.
2) As a X and Y values I supply dynamic measures hidden in 2 slicers.
3) These measures are calculated as SWITCH(MIN([index]); 1; [measure1]; 2; [measure2].....) up to 38 values both .
4) When I choose one slicer and second slicer, it takes minute or two to calculate and display scatter chart.
Hope you got the idea, it is pretty popular way to slice table by columns, rather than rows.
Thanks a lot,
Kareem
5ere used to be an issue where if statements and switch would evaluate every possible answer (eg 38 in total) even though you only need 1 of them. I heard this was fixed, but maybe not.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the September 2025 Power BI update to learn about new features.