Need help to understand why query plan change

[Anonymous]

Hi!

I'm really need your help. I have spent alot of hours trying to get the same query plan for this.
I am using a slicer in Power BI to select the metric I want to analyze.
But the query plan will totaly change. It will generate a full table scan on one realy big table.
In the normal case I use the switch statement but to minimize to

[lbendlin]

I don't understand how your last comment is related to your original issue.

Have you considered inlining the measure code?

[Anonymous]

The reason for I'm digging in to this is the performance.
When I'm using [# of rows with Police dispatched by] in a visual direct, the response is under 1 second.
If I replace it with [Metric to show] the response is ~15 seconds.
I thought it was almost the same, just a simple check before returning the same metric.

Metric to show =

SWITCH(

[Selected Metric Name],

"# of rows with Undefined",[# of rows with Undefined],

"# of rows with Incident Header]",[# of rows with Incident Header],

"# of rows with Police dispatched by",[# of rows with Police dispatched by],

BLANK()

)

[lbendlin]

in your case you don't need to use selectedvalue since you are already in the filter context and are not doing any context transition in your measure.

You use nested measures, however.  If you are concerned about performance then you will want to rewrite this to avoid calling one measure from another. In such a scenario it is better to be explicit and inline all the code.