What if parameter

[Bhavyamalik149]

I have a what if parameter and its min value is 0, highest is 10000000, increemnent is 1 and default value is 10000000... I want to see data for let's say 55 but it is not showing... if I keep the highest value as 100 or 1000 then I'm able to see but not otherwise, can anyone tell how can I achieve it with 10000000 as the highest value and with '1' increment...thanks 

[v-sgandrathi · Accepted solution]

Hi @Bhavyamalik149,

Thank you @danextian , @Royel  and @DataNinja777 for your continuous response to the issues in the forum.

Has your issue been resolved?
If the response provided by the community member addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.

Thank you for your understanding!

[v-sgandrathi]

Hi @Bhavyamalik149,

Just looping back one last time to check if everything's good on your end. Let me know if you need any final support happy to assist if anything’s still open.

Thank you.

[danextian]

Hi @Bhavyamalik149 ,

That’s a known limitation of what-if parameter tables—if the range is too large, selecting an exact value with the single-select option becomes difficult. A workaround is to use the less than or equal to or greater than or equal to options. Then, cover the grayed-out box with a shape and add a text box on top. Finally, group the slicer, shape, and text box together, and ensure Maintain layer order is enabled under General settings > Properties.

Please see the attached pbix.

Bud do you really need a what-if parameter table with 10M rows? I can imagine the memory it will take given the sheer amount of distinct values.

[Royel]

Hi @Bhavyamalik149  if you make your slicer style between then you can easily achieve this. 

[DataNinja777]

Hi @Bhavyamalik149 ,

Of course. The issue you are encountering stems from the sheer number of distinct values you are asking the software to generate. When you set a parameter with a minimum of 0, a maximum of 10,000,000, and an increment of 1, you are creating a list with over ten million individual entries. For performance reasons and to prevent the application from freezing or crashing, the software automatically truncates the list of options it displays in the visual slicer. This is why you cannot scroll down to or see a small number like 55; the visual is only showing a small fraction of the total possible values. The reason it works with a smaller maximum, such as 1000, is that a list of a thousand items is manageable for the application to display.

The most effective solution is to change how you interact with the parameter on the report. Instead of trying to select a value from an impossibly long list, you can alter the slicer to become an input box. This allows you to simply type the exact number you need. In a tool like Power BI, you can achieve this by selecting the slicer visual, navigating to its formatting options, and under the slicer settings, changing the style from a list or dropdown to an option like "Between" or "Less than or equal to." This will convert the slicer into input boxes where you can directly enter the value 55, bypassing the need to scroll through millions of options.

An alternative approach, if you want to maintain a sense of interactive selection, is to use two separate parameters that work together. You could create a "coarse" parameter for the larger increments, perhaps ranging from 0 to 10,000, and a "fine" parameter for the smaller values, ranging from 0 to 999. In your calculations, you would then create a measure that combines the input from both slicers, for instance by multiplying the coarse value by 1000 and adding the fine value. To select a value like 55, you would simply choose 0 on the coarse slicer and 55 on the fine slicer. This method keeps the slicers responsive and manageable while still giving you precise control over the full range of numbers.

Best regards,