Large Numeric values in FlexGrid - editable cells

Posted by: rasika.sinha on 18 September 2017, 9:53 pm EST

  • Posted 18 September 2017, 9:53 pm EST

    Hi Team,

    I need to display and edit large decimal values in the flex grid for number and currency formats till 10 decimal precision.

    But the grid’s editor behaves weird for large values - for example if i enter 50925000.1234567899, on cellEditEnded the value becomes 50,925,001.123456791043

    Is there any max limit for numeric values in the grid?

    I tried to use the custom cell editors but they do not accept NULL values therefore it is not suitable for my requirement. Even that does not works with the number mentioned above.

    In the fiddle http://jsfiddle.net/qwctfo4y/ , you can change the format to n10 and c10 to reproduce the issue.

    Please replay ASAP

    Thank you

  • Posted 18 September 2017, 11:50 pm EST

    An update in the above issue, I used isRequired property so that it accepts null as well but the major issue of large numbers with 10 decimal precision persists.

    Please let me know ASAP.

  • Posted 19 September 2017, 10:50 pm EST

    Hi Rasika,

    As I can observe that “50925000.1234567899” changes to “50925000.1234567910” after cell edit end. The same can be observed with the toFixed() method , you can try the following:

    (50925000.1234567899).toFixed(10) => 50925000.1234567910

    We are able to replicate the issue with InputNumber and it has been escalated to the concerned team for further investigation with internal tracking id #286926.

    We will let you know as we get any update on this.

    Build Version used : 5.20172.334

    Thanks,

    Manish Kumar Gupta

  • Posted 21 September 2017, 11:02 pm EST

    Hi Manish,

    Do we have any ETA for the fix? Will you be sharing any piece of code as solution or it will get published in an upcoming release?

    Also are there interim issues with the forum’s site these days, yesterday this link was routing me to page not found?

    Thank you,

    Rasika Sinha

  • Posted 25 September 2017, 4:52 pm EST

    Hi,

    The issue is with the team and we can not estimate time for fixing this.

    The web team is working on the issues, hence this may cause to this problem.

    Thanks,

    Manish Kumar Gupta

  • Posted 5 January 2018, 12:43 am EST

    Hi Manish,

    Do we have any ETA for the fix? Its been few months now?

    Thank you!

  • Posted 6 January 2018, 12:14 am EST

    Hi Rasika,

    We are sorry for the late reply.

    Before replying, we would like to let you know something:

    Every language, incluiding JavaScript, has precision limits when dealing with numbers.

    If you need more precision than that, you should probably be using dedicated numerical packages.such as the ones here:

    https://github.com/MikeMcl

    However, this issue seems to fix this issue with build 5.20173.400. Please refer to the fiddle:

    http://jsfiddle.net/qwctfo4y/44/

    If you would like to verify the issue, you may download the pre-release build for testing purpose.

    http://prerelease.componentone.com/wijmo5/

    This build is not recommended to use for production since this is under QA process for next release.

    ~Manish

  • Posted 16 January 2018, 12:29 am EST

    Hi Manish,

    I tried the fiddle, now “50925000.1234567899” changes to “50,925,000.1234567900”, “50925000.1234568787” changes to “50,925,000.1234568800”, hence my issue still persists.

    Regarding the precision limit, we just want it till 10 decimal precision which should be doable without any other external library. Also even if I consume a library but if wijmo’s in-grid editor changes the value entered by user then it would not fix this issue.

    Please let me know further update on this issue.

    Thank you,

    Rasika.

  • Posted 6 June 2018, 8:53 pm EST

    Hi Manish,

    Any update on this issue?

    Thank you,

    Rasika.

  • Posted 18 June 2018, 9:36 pm EST

    Hi Manish,

    Any update on this issue?

    Thank you,

    Rasika.

  • Posted 21 February 2019, 10:26 am EST

    Hi,

    We’re also having the same issue. Any update on this?

    Thanks,

    Johnny

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels