What-if Parameter Slicer Limitations
What-if Parameter Slicer has a limitation on the number of values. If too many, "Showing Representative Sample" Error appears. It appears that 1,000 values is the limit. Is it possible to expand the limit?
Kjell Larsen commented
This needs to be fixed. A work-around (that doesnt work for me) could be to let the user put in values in thousands, then you just adjust for that in the model. Expands your inputs from 1000 to 1000 000.
Just ran into this limitation for the first time. Very frustrating, and it severely limits the applications of the What-If parameters.
Hassan Obeidat commented
Try creating a parameter adhering to the initial limitation, then when you choose the parameter table from the Fields pane, you will find that its function is something like this:
GENERATESERIES(0, 100, 1)
You can play with this formula and see where the limit really is.
Major limitation as built models on the what if parameters become virtually useless!
it would be much practical if we can enter any values for what if analysis.
Neal Levin commented
Agree this is a major limitation. i recommended this to my client only to realize it is too limited to be useful.
Great idea, cause it's really restrict opportunity to create interesting models. Please, remove this limitation
Olivier BEAUJEU commented
Yes, limited to 1000 values is a nightmare.
It is reached really fast.
For example 0 to 100% by 0.1 increment gives 1001 rows :) (reached !)...
Please remove this limit.
Quite annoying limitation.
Also frustrated by this issue. Noticed that use "tab" to commit whatif values causes the word "Single" to be shown. check my video here - https://www.useloom.com/share/231d24e80fb1449d8ee00df4cb7d4b19
wow this limitation sucks....really...only 1000 values, Microsoft come on, ruined my day, after spending two days building some model that is using what-if parameter...I noticed the rounding in some of my inputs.....I just can't believe it
Like others I would like to see this increased. I use What-If parameters to allow users to enter the cost price of an item which can vary from month to month. As the cost uses decimal places then you will see how small of a range I have.
With this row limit it means I have to change the range of my parameter each month which is a pain.
Hi, Is This option available for Direct Query mode??
Roberto Massucco commented
Is it possible to remove this limitation?
Jordan Wenzlick commented
Needs to be fixed - feature is severely limited right now. How did this not get noticed before being released?
I agree that the limit needs to be increased. It is very frustrating to get a "Representative Sample" when I want it to be a single value.