Numeric Range Parameters is not working - 2024

[huseyincenik]

I created a numeric range parameter. I used the parameter in TOPN, but the parameter does not appear in TOPN. When I add the parameter value as a column to a chart, I see the value I selected. but in Dax code it returns 0 from the parameter. Normally it's at 6 now, but it doesn't reach 6.

[jaryszek]

So how to make this working? 

[Anonymous · Accepted solution]

Thanks for your concern about this issue, @Jihwan_Kim .

And @huseyincenik , I would like to add a few points that may be helpful. Your formula is returned to the calculated table, which is a static result. It does not dynamically return results based on the dynamic filtering of slicers or filters.

In Power BI, there are three fields that can be created: Measure, Calculated Column, and Calculated Table.

Measures are dynamic, while calculated columns and calculated tables are static.

About more differences or details among them, you could refer to

Measure vs Calculated Column: The Mysterious Question? Not! - RADACAD

In summary, numeric range parameter is not available in calculated column or calculated table which is set by default.

In fact, in the official document provided by Jihwan, this sentence also confirms this.

Best Regards,

Stephen Tao

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

[huseyincenik]

Thank you @Anonymous .Would you consider this as user feedback and update PowerBI on this issue? It's really interesting that this doesn't happen. Why do we do TOPN filtering only in a limited way via filter? This also works in other BI Tools like Tableau!

[Jihwan_Kim]

Hi, 

I am not sure if I understood your question correctly, but if you want to use the numeric parameter inside the dax formula that results a table, please check the limitation in the link below.

I hope this helps.

Use parameters to visualize variables - Power BI | Microsoft Learn

[huseyincenik]

Thank you for your answer. My parameter is created between 1 and 20 and aims to display TOPN. It is not affected by the restrictions you specify. What surprises me is that it appears when I define the parameter as values in a chart. But when I write it in dax as above, it is taken as 0.