Filter function in connection with parameters

[Stan11]

Hello!

I am trying to use the filter function with parameters.

Desired behavior would be that all rows with an ID>3 are not displayed.

Unfortunately, the value "0" is always transferred. That means, all 6 rows are displayed.

No matter what I set with the slider.

(First screenshot)

If I write the "3" directly in the dax expression, it works.

(Secound screenshot)

What am I doing wrong?

[serpiva64]

Hi,

take a look at this exemple

[Stan11]

Does this mean, that only with the "filter" function, my example does not work?

And that I have to use the "calculate" function additionally?

[jst_jdennis]

Based on what you've shared, it seems like the issue may be with the way you're passing the parameter value to the filter function.

In your first DAX expression, you're using the following syntax to pass the parameter value to the filter function:

'Parameter'[Parameter-Wert]

This syntax is correct for referencing the parameter value in your DAX expression. However, it's possible that the issue is with the way the parameter is defined in your report. Make sure that the parameter is correctly defined as a numeric value in your report, and that the name and spelling of the parameter match what you're using in your DAX expression.

In your second DAX expression, you're directly referencing the value "3" in the filter function. This works because the value is hardcoded into the expression. If you want to use a parameter value instead, you can modify the expression to use the same syntax as in your first expression:

Tabelle = FILTER(farben1, farben1[ID] > 'Parameter'[Parameter-Wert])

This should filter out all rows with an ID greater than the parameter value.

I hope this helps! Let me know if you have any further questions.

Credit: ChatGPT | DAX filter function issue. (openai.com)

[Stan11]

I just checked it again. Both the IDs and the table with the parameters are defined as integer / whole number (= Ganze Zahl)

I also tried it once by converting both to decimal. Unfortunately it does not work there either.