Forum Discussion
Post PartisanSlicer input box misbehaving
Hi,
Has anyone experienced any issues manually entering a value in a slicer box?
I try to enter 15 and it puts in 16.
I try to enter 20 and it puts in 19.
I try to enter 21 and it puts in 22.
Can't see to get the number I try to enter.
Thanks,
Here is the code for the measure:
SelectedValue = SELECTEDVALUE('NumberRange'[Value], 0)Replace 'NumberRange' with your calculated table name.
Replace [Value] with the column name from that table.
Did it work? 👍 A kudos would be appreciated
🟨 Mark it as a solution to help spread knowledge 💡
11 Replies
- DataVitalizer
Super User
Hi mp390988
Is your slicer based on a What-If parameter or a regular field from a table?Did it work? 👍 A kudos would be appreciated
🟨 Mark it as a solution to help spread knowledge 💡 
mp390988- DataVitalizer
Try to switch the slicer to Dropdown mode instead of the input box, or alternatively use a numeric slicer based on a separate integer column (1 to 3000) instead of the What-If parameter to allow precise manual entry without snapping errors.
Did it work? 👍 A kudos would be appreciated
🟨 Mark it as a solution to help spread knowledge 💡- mp390988
so should I create a calculated table using GENERATESERIES?
I realised my customerCount measure display over 10 thousand customers.So I need to put the name of the measure in my Generateseries
v-kpoloju-msftCommunity Support
Hi mp390988,
Thank you for reaching out to the Microsoft fabric community forum. Also, thanks to DataVitalizer, for his inputs on this thread. Here I provided some steps those might be resolve the issue which is you faced. Please go through the below steps. Yes, this is a known behaviour in Power BI, and it can be a bit confusing at first.
What is likely happening here is that the slicer is connected to a column that does not include every number in the range you are trying to enter. So, when you type something like “15,” but “15” does not actually exist in the data, Power BI automatically jumps to the closest available number like “16” or “14.”
To fix this, there are a couple of reliable options:
- Use a What-if parameter: This lets you create a slicer with a smooth numeric input experience that accepts every value in a defined range. Here’s the official doc on that:
Use parameters to visualize variables - Power BI | Microsoft Learn - Use a helper table with GENERATESERIES(): This creates a continuous list of numbers (e.g., 1 to 100) so the slicer can accept whatever you type. Here’s the DAX function you can use:
GENERATESERIES function - DAX | Microsoft Learn
For general info on how slicers behave, this doc is also useful:
Slicers in Power BI - Power BI | Microsoft Learn
Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.
Thank you for using the Microsoft Fabric Community Forum.- v-kpoloju-msft
Hi mp390988,
Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.Thank you.
- v-kpoloju-msft
Hi mp390988,
Hope you had a chance to try out the solution shared earlier. Let us know if anything needs further clarification or if there's an update from your side always here to help.Thank you.
- Use a What-if parameter: This lets you create a slicer with a smooth numeric input experience that accepts every value in a defined range. Here’s the official doc on that: