Input value parameter not working

[AFoisAnalytics]

Hello everyone,

I created a numeric parameter (Modeling -> New paramter -> Numeric range) with range from 1 to 10,000,000 with increment of 1. I will use this parameter to parametrize a query.

The problem is that the text box where is possible input the desired value it doesn't work.
For example If i type:

• 5 the input box show again 1 ( the starting value)
• 1,000 the parameter return to 1
• 5,000 the parameter go to 9,991
• 20,000 the parameter goes to 19,891

What is going on? Why the parameter is having this behavior?

Starting Value ParameterTyping 5000 as input parameterHow the parameter respond with wrong value selection

[AFoisAnalytics]

Thank you all for the replies, so the answer is that in 2024 this problem is still NOT been resolved.

Anyway I think that is just ridiculous that Microsoft spend time and resources developing useless features to wright orrible dax with Copilot but don't fix such essectial functionality.

The solution to creare a Text column of 10,000,000 and ask the Customer (User) to scroll a dropdown list until he arrive to the number he wants is horrendous.

I am migrating a report from Tableau to Power BI and in Tableau you can just creare a parameter where you type the number you want and the software build dynamically the parameter after. So much easier and user-consumer-friendly.

[SamWiseOwl]

Hi @AFoisAnalytics if you click on the ...  on the right hand side of your slicer you can choose search on.

That way you can have them type in the search box instead.

Alternatively there are custom slicers free that will filter as soon as they search.

[danextian · Accepted solution]

Hi @AFoisAnalytics 

Sampling  occurs when too many values are in the column used in parameter. It is a known issue. Unfortunately, it hasn't been addressed yet
https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=3cd3bbbc-7589-4696-b7f8-e0f1d08b3c42

Alternatively, you can add a text column to the table and use that in a dropdown slicer instead. Just make sure to sort it by the original parameter column.

[SamWiseOwl]

Hi @AFoisAnalytics 

Performance on large sets (10 million in this case) is not always reliable.

Do you need every value seperate or could you use the Step feature to reduce the number of rows.

Parameter = GENERATESERIES(1, 10000000, 10000)

This will reduce the number of rows from 10million to 1 thousand.

[AFoisAnalytics]

Hi Sam, unfortunately i need every possible value. I am querying a very large database from Snowflake and the parameter will be used to parametrize the Sql query received by power query. 

The report has to be in direct query mode and because of the size of the data model the parametrization is necessary. Build a table with a Text column and materialize upfront all possible values is creazy for me. This makes the model much heavier with many useless MB of data inside.

I am shocked by Microsoft that a Text column is the only solution or workaround.

[VijayP]

@AFoisAnalytics  This is because of too many values in parameter . you need to make it as a column and choose from column to avoid that issue