Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Hi everyone,
I am working on a Power BI report and I encountered an issue with data range slicer input. Currently, the slicer only accepts a period (.) for decimal input instead of a comma (,). This is causing some confusion for users who are accustomed to using a comma for decimal numbers. In Germany, the comma (,) is commonly used as the decimal separator.
Is there a way to configure the data range slicer to accept a comma (,) as the decimal separator instead of a period (.)? Any help or guidance on how to address this issue would be greatly appreciated.
Thank you!
When there is no input it is shown correctly:
As soon as you want to edit:
Solved! Go to Solution.
It's important to note that while DAX and the Power BI interface support localized number formats, certain visual elements like the data range slicer may not fully adhere to these settings due to their specific implementation.
The slicer's behavior of accepting only periods (.) for decimal input, regardless of regional settings, is a known limitation.
You may need to explain this to your users.
Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi Nono Chen,
Thank you for your response. I understand that by default, DAX uses commas (,) to separate items in a list and periods (.) to indicate the decimal place, and that these can be adjusted based on Windows locale settings.
However, even though all my language settings are set to German and the DAX separator is set to regional settings, the data range slicer still only accepts periods (.) for decimal input. This is causing confusion for my users, who are accustomed to using a comma (,) as the decimal separator in Germany.
Is there any other configuration or workaround that might address this issue specifically for the data range slicer? Any additional help would be greatly appreciated.
Thank you!
It's important to note that while DAX and the Power BI interface support localized number formats, certain visual elements like the data range slicer may not fully adhere to these settings due to their specific implementation.
The slicer's behavior of accepting only periods (.) for decimal input, regardless of regional settings, is a known limitation.
You may need to explain this to your users.
Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
By default, DAX uses commas (,) to separate items in a list and periods (.) to indicate the decimal place in a number. While we do recommend using the defaults, you can use the DAX separators based on your Windows locale settings.
You can view the link below for more details:
Supported languages and countries/regions for Power BI - Power BI | Microsoft Learn
I hope this helps.
Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the October 2025 Power BI update to learn about new features.