Appian Converting the decimal value to a nearest integer

RE: Appian Converting the decimal value to a nearest integer

manishk114 — Wed, 26 Jul 2023 09:11:16 GMT

Faced the same issue today, used the test function to resolve it .

-> use convert json to appian value in integration.

->go to the node and then format it with the pattern you want like below.

->Use the Text (index(local!body,"node","node",{}),"######.##")

this will give you the data which comes in raw

RE: Appian Converting the decimal value to a nearest integer

Stefan Helzle — Tue, 11 Jul 2023 11:58:13 GMT

This is just a display "issue". When turning a number into string for display purposes, Appian rounds aggressively. You can find a gazillion of discussions on that topic here.

Nothing wrong! Just go on.

RE: Appian Converting the decimal value to a nearest integer

philippem0001 — Tue, 11 Jul 2023 11:47:32 GMT

Hi, I have the same problem.

The integration with the api don't return the right value with "convert json to appian value" ( 162132.8 instead of 162132.79 ).

I put the image with "converting json to appian value" (162132.8) : and the image with raw text (162132.79 ):

The api returns a number (double) - test with postman :

"capitalContingency": {

"value": 162132.79,

"currency": "EUR"

RE: Appian Converting the decimal value to a nearest integer

adithyay — Tue, 09 Jul 2019 15:30:50 GMT

No, I'm not casting it, it is the output which I see when I call an API which has a json response.

RE: Appian Converting the decimal value to a nearest integer

Nathan Hunter — Thu, 04 Jul 2019 21:36:32 GMT

That's odd. Normally the decimal value should stay the same. I have just run a test by using a!fromJson(a!toJson({number:42103.95})) and it worked fine.

Are you casting it to a CDT using cast()? If so, if an integer data type has the corresponding keyword it will remove the decimal value to convert it into an integer - for example tointeger(42103.95) returns 42103.95

If not, could you either copy and paste your SAIL or upload a screenshot?