Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Shape the future of the Fabric Community! Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions. Take survey.

Reply
Anonymous
Not applicable

What If Slicer - Single Value - Autocorrecting Issue

Hi all,

 

I am having trouble understanding why my single value slicer is behaving like this:

 

Here, I am typing out the target I want to set in my "What If" slicer.

 Single Value Slicer - Typing.PNG

 

 

 

 

 

 

 

 

This is what happens when I press enter:

Single Value Slicer - Enter.PNG

It seems the field autocorrects to a value close(?) to the value I entered.

 

If I switch the slicer to a drop down list, then I can see the value I originally wanted.Drop Down Slicer - Selecting.PNG

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Has anyone else also experienced this issue?

I know there is no issue with decimal places because I've tried increasing it with the issue still occuring.

I have also tried not setting the Data Format to Percentage but still no luck.

 

Any help, even letting me know this is a known bug, would be great.

 

Cheers, Leo.

1 ACCEPTED SOLUTION

Hi @Anonymous,


When you click the ! button on the left above, it shows the following tips. It's because of the range being too big and the numbers are being sampled. So not all value can be typed as single value.

1.PNG

There are the same cases below for your reference.  

What if parameter help - input changes by itself after hitting enter
Whatif Parameter issues 

Best Regards,
Angelia

View solution in original post

9 REPLIES 9
mustafaasiroglu
Microsoft Employee
Microsoft Employee

Hello everyone,

 

I also faced with this annoying behavior and found a workaround. Just wanted to share here wishing it helps others.

 

After creating what-if parameter, change slicer type to "greater than" or "between" instead of "single value". And then, change default measure formula to MIN(parametercolumn) instead of SELECTEDVALUE(paramentercolumn,0).

 

Lastly, you can hide slider handle using format pane and hide second input box by resizing the visual.

 

Done: End user experience is same and we have full list of values available!

Great workaround, thanks for that!

Phil_Seamark
Microsoft Employee
Microsoft Employee

What is the forumla for the GENERATESERIES function for the parameter?

 

I changed mine to this

 

Parameter= GENERATESERIES(0.0001, 20, .00001)

and it worked for me.  You can change the upper, lower and increment values to suit.


To learn more about DAX visit : aka.ms/practicalDAX

Proud to be a Datanaut!

Anonymous
Not applicable

Here's the formula I was using (it was created by the What If tool in Power BI):

Util Target = GENERATESERIES(0, 1, 0.0001)

Thanks for the suggestion but still no luck.

 

I've also tried:

GENERATESERIES(0.00001, 20, .00001)
GENERATESERIES(0.00001, 20, 0.00001)
GENERATESERIES(0, 20, .00001)

If it has worked for you, it may be a problem with what I am trying to filter?

Anonymous
Not applicable

I've tried using the slicer in its own page but here's what I get when I enter:

0.9866

 Single Value Slicer - Enter (2).PNG

 

 

 

 

Hi @Anonymous,


When you click the ! button on the left above, it shows the following tips. It's because of the range being too big and the numbers are being sampled. So not all value can be typed as single value.

1.PNG

There are the same cases below for your reference.  

What if parameter help - input changes by itself after hitting enter
Whatif Parameter issues 

Best Regards,
Angelia

So... As this is for this many choices of input using only sample range of values, thus making input impossible, you could also (if you still want users to narrow down numbers by input):

 1. Add an extra column to the parameter table with selectable values AS TEXT e.g. using FORMAT function

 2. Add a slicer with dropdown and Search field, using the newly created column which will allow for it.

 

voila. not that awesome. but works.

 

yashczoor_0-1668603977076.png 

yashczoor_1-1668603987458.png

 

 

Anonymous
Not applicable

I also found this known issue pretty frustrating, as I had to modify my solution to allow for only 1000 values.
I also noticed that on entry of whatif values, different things happen depending on if you click "enter", "tab" or just click in the next entry box. Check this out one this video here - https://www.useloom.com/share/231d24e80fb1449d8ee00df4cb7d4b19

 

 ROI_Calculator_Tab_Single_Issue_2018-07-11_1401.png

 

 

 

 

Could be.  Check the format settings of both the Parameter calculated measure and the item you are filtering.


To learn more about DAX visit : aka.ms/practicalDAX

Proud to be a Datanaut!

Helpful resources

Announcements
November Carousel

Fabric Community Update - November 2024

Find out what's new and trending in the Fabric Community.

Dec Fabric Community Survey

We want your feedback!

Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.

Live Sessions with Fabric DB

Be one of the first to start using Fabric Databases

Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.