-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On CRUD Form numeric field (with format #,##0.00) when updated becomes zero 0 [Label: bug & feature] #296
Comments
borisdj
changed the title
On CRUD Form numeric field (with format #,###.00) when updated becomes zero 0
On CRUD Form numeric field (with format #,##0.00) when updated becomes zero 0
Jun 28, 2021
borisdj
changed the title
On CRUD Form numeric field (with format #,##0.00) when updated becomes zero 0
On CRUD Form numeric field (with format #,##0.00) when updated becomes zero 0 [Label: bug & feature]
Jun 28, 2021
gustavnavar
added a commit
that referenced
this issue
Jul 16, 2021
Package 2.1.18 implements your fix. This sample implements it for the Freight field: https://gridblazor.azurewebsites.net/crud Thanks for your fix |
Glad to help. |
rgentry09
pushed a commit
to rgentry09/ERP-ASP.NET
that referenced
this issue
Jul 10, 2023
dev0926
added a commit
to dev0926/gridNET
that referenced
this issue
Feb 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Numeric field with thousands separator when updated gets 0.00 value instead of actual.
To Reproduce
Steps to reproduce the behavior:
IN CODE - Set Format:
c.Add(o => o.Amount).Format("{0:#,##0.00}");
ON FORM
Add ___________________
Added ________________
**
Update _______________
Updated ______________
Expected behavior
After update Amount should be 1,234.57.
Currently only way for getting correct value is when editing number with 4+ digits to always delete thousands separators in the field and then Save the Form.
Fix should parse correctly separator to number, or not to be shown in the field at all.
Also to note that when using localization de-DE and some other European languages, comma and dot are inverted:
1.234,56
But bug is the same, also goes to zero.
Additionaly it would be best if Field could be configured in such way that thousands separator is shown both when Adding or Updating on FocusOut when switching input to another field. In that case when that number is in Focus then thousands separator is removed in both cases since it can interfere with typing digits. This format is useful to avoid mistakes when typing large numbers.
The text was updated successfully, but these errors were encountered: