-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
Excel Export: Negative values converted to positive #1135
Comments
trying out Example 14 which has negative numbers, it works as expected and unless you provide a repro, I can't help much. So as far as I see, it works correctly and there must be some issues with your code. |
I removed the |
I was able to reproduce, will do a bug fix shortly |
- fixes an issue identified in Angular-Slickgrid where the negative numbers were seeing negative numbers turned to positive numbers (ref: ghiscoding/Angular-Slickgrid#1135) - also improve perf of `exportWithFormatterWhenDefined` by analyzing `exportWithFormatter` only once instead of twice
- fixes an issue identified in Angular-Slickgrid where the negative numbers were seeing negative numbers turned to positive numbers (ref: ghiscoding/Angular-Slickgrid#1135) - also improve perf of `exportWithFormatterWhenDefined` by analyzing `exportWithFormatter` only once instead of twice
…-numbers fix(export): fix negative number exports to Excel, fixes #1135
fixed in Angular-Slickgrid v5.6.4 and Slickgrid-Universal v2.6.4, you can also test it with the live demo Example 19 Also note this is the last version before the next upcoming Angular-Slickgrid v6 major version |
Describe the bug
I've been trying to export a table that contains a fieldtype of number.
This is how it's displayed to the UI table
When i tried to export using ExcelExportService, I get this
I tried the CSV export, and i got it correctly.
Reproduction
Have a dataset that contains negative numbers, and set it to fieldtype.number
export using ExcelExportService
Expectation
No response
Environment Info
Validations
The text was updated successfully, but these errors were encountered: