Closed juhalassila closed 4 years ago
I think I was able to narrow down this issue to locale settings.
Looks like this component doesn't handle decimals correctly when numbers are presented with a decimal comma (instead of decimal point).
Initially observed this issue with Finnish locale setting
Switched to English (United States): desimals got saved OK
Switched back to Finnish: observed the issue again.
Just to be clear
Aaa... maybe this issue is related to this "feature":
Restrictions
I'm assuming that the ability to handle non-integer numbers (and percentages) is on the roadmap. Or is it?
Of course, I desperately need this feature right now.
Unfortunately, I'm not a developer. Therefore, I'm not in a position to contribute in fixing of this issue.
But let me put it this way
I'm looking into this now to see if I can find out why this is happening.
Just want to let everyone know that I handled our mobile data collection requirement using FormTitan. Therefore, the money is not on the table anymore.
I'm glad you found a solution.
Hi! Looks like I have an issue with decimals. I have a number (12,4) field that I can inline edit in datatableV2.
Pls see attached PPTX for screenshots of
KK - Salesforce - Datatable BUG - 2020-08-01_0723.pptx