Parameter changeValueAsync with percentages expects comma instead of point
See original GitHub issueReproducable example: try the Parameter.changeValueAsync method on the Superstore workbook to change the “Churn rate” parameter.
parameter.changeValueAsync(0.1); // 25%
parameter.changeValueAsync("0.1"); // 25%
parameter.changeValueAsync("0,1"); // 10%
This is especially confusing because it will return DataValue.value === "0.1"
(point not comma 😖)
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
sql server - Show comma instead of point as decimal separator
I just want to get the right number format here in germany, so i need to show commas as decimal separator instead of...
Read more >How to Change Commas to Decimal Points and Vice Versa in ...
Depending on your country or region, Excel may display decimal points or dots instead of commas for larger numbers. The decimal point (.)...
Read more >Solved: Commas and dots formatting - Qlik Community - 808790
Solved: In my locality we use a dot as a thousand separator an a comma for decimal. i.e. SET ThousandSep='.'; SET DecimalSep=','; SET...
Read more >Solved: Thousand-Separator-and-Decimal-Separator
Solved: hello, for the currency column, I'm having problems with decimal separator and thousand separator. Decimal separator is a comma and thousand.
Read more >How to Convert Comma to Decimal Point & Dot to ... - YouTube
This will be useful if you are asking the following questions: Why does Excel use a comma instead of a decimal point ?...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We’re taking a look at this.
Yep, I agree with all of that. We’ll look into it soon, but I’m not sure whether any related fixes will be in v1 of Extensions API or post-v1. And if it’s post-v1, we’ll have to be sure to not make breaking changes.