Hello communityI am currently thinking a lot of the kind of super limited way of appian dealing with big decimal numbers.Example:
12313139.1 as input will result in:
1.231314e+07
If you want to transfer this number via API (JSON input) that will cause issues as the receiving system cannot deal with the ‘e+07’ in the end.
-> is there any other approach to solve this except converting it into a string? The API developer will think we are unreasonable to have a decimal regardless how big, should be a text. Its not helping appians reputation withing the clients company there.(and i can understand their thinking)
What are your thoughts on that? Do I miss there something?
Discussion posts and replies are publicly visible
This has been discussed a hundred times here. This is just the way the decimal is formatted. When I turn a dictionary with a decimal value into JSON, I do see all digits.
Perhaps I am doing something wrong here, but thats a statement I am currently not agreeing to
This does match the JSON specification to the point. Exponential notation is part of it.
aaah i am missing JSON knowledge here.here we go. but doesn't make this exponential conversion the delivered number less precise? Could JSON deal with 123456789 instead of an e factor?
Any decimal in a computer is limited by its binary nature. You will need to check whether your use case is affected by these limits and design accordingly.
I think we are reaching certain limits of 32 bit design here.Thank you, sometimes an exchanges helps a lot to get some ideas:)