Forum Discussion
What If Parameter Issue
I've got 2 What if Parameters with formulas "Expense What If = GENERATESERIES(0, 300000, 1)" and "Budget What If = GENERATESERIES(0, 300000, 1)"
When I put the "What If Parameter" to "Single Value" and type in a single value, I get an "i" in the top left that says
"Too many Expense What if Values. Showing a representative sample. Filter the data or choose another field."
What is the point of picking a single value if it won't actually let me pick a single value?
I am essentially trying to make a field that subtracts "expense" from "budget" using the what if parameters. If anyone could help me do this another way I would very much appreciate the help.
9 Replies
I created an Idea request for this if we want to try and create some traction to get PowerBI to increase the limitation...
Looks like someone created a request already:
Use a combination of UNION() and GENERATESERIES() such as the following, enabling scale within your What If Parameter, as well as enabling Power BI to manage the number of parameters it has to hold in memory.:
UNION(
GENERATESERIES(0,500,10)
,GENERATESERIES(1000,10000,1000)
,GENERATESERIES(20000,100000,20000))
I don't think the issue is getting the values in the table, it's the slicer won't take more than ~1,000 values when it's looking at a parameter.
A workaround may be to do what you were doing by unioning a few different GENERATESERIES() functions to give granularity and further detail in the important ranges.
HI ahines
I thnk the idea is the table generated by the "What If Parameter" is to be used in a slicer. This will then allow you to pick an individual value from your list of 1 to 300,000.
It's the individual value that you can incorporate into your other measures. This way, when you adjust the slicer using your what if measure table, any other measure that references the 'single' measure will recalculate and show the updated value.
Phil_Seamark i think the issue ahines mentioned is that user cannot enter single value in the box and I tried it by myselft and if I enter some number, it round off to next number. I think that is the issue ahines is trying to explain and totally agree with him
HI parry2k
Oh yeah, it seems the slicer can't cope with that number of rows.
looks like values GENERATESERIES(1, 99998,1) might work or GENERATESERIES (1,300000,3)
Seems to be based on the number or rows.....
