Custom object to JSON change value 1234 to 1234.0

(2) Share

Report

Posted on by alexlee985

Hi all, i encountered this issue when converting custom object to json.
The value in object is 1970

However once i convert it to json (as i need json for Webservice call), the value 1970 become 1970.0

My step is

Any help to resolve this is very appreciated.

Categories:

Power Automate Desktop

I have the same question (0)

All responses (12)

Answers (0)

rb0 9 on at

Like (0)

Report

hi @alexlee985
I ran into the same problem. Were you able to find a solution? Digging the internet did not help so far.
I even tried to use the "Convert text to number" action in hopes that it would pick it up as interger, but no avail. I it really the "Convert custom object to JSON" action that is messing it up. The docs state that the returned value is Text. But why it also converts integer to decimal. So weird. Maybe I'm missing something.

Was this reply helpful? Yes No
rb0 9 on at

Like (0)

Report

I believe this is a bug, PAD version I am using is 2.18.146.22083
To reproduce follow these steps:
SET DataTable TO { ^['ProductID', 'ProductName'], [1, 'FirstProduct'], [2, 'SecondProduct'] }
SET CustomObject TO {{ }}
SET CustomObject['Table'] TO DataTable
Variables.ConvertCustomObjectToJson CustomObject: CustomObject Json=> CustomObjectAsJson

Resulting JSON:
{"Table":[{"ProductID":1.0,"ProductName":"FirstProduct"},{"ProductID":2.0,"ProductName":"SecondProduct"}]}

Hi @John_Mavridis ,
Hope you are doing well!
tagging you here as you replied on another JSON related issue. Could you please review this thread and inform if this is a bug. For some reason integer values become decimal when exporting to JSON.
Thank you in advance,
Rob

Was this reply helpful? Yes No
rb0 9 on at

Like (0)

Report

too bad this is not resolved in 2.21.244.22174 ☹️
especially considering the fact that the new feature of json editor is added.
disappointing.

Was this reply helpful? Yes No
rb0 9 on at

Like (0)

Report

This is still an issue in 2.28.135.23016☹️

Was this reply helpful? Yes No
Cristpb 23 on at

Like (1)

Report

No fixing this error yet, right? version: 2.30.109.23075

Was this reply helpful? Yes No
lingdongxinling 10 on at

Like (1)

Report

Yes, I use the same version like yours, the same error.

Was this reply helpful? Yes No
Riyaz_riz11 3,844 Super User 2025 Season 2 on at

Like (0)

Report

Hi @rb0 @alexlee985 @lingdongxinling
Try using this

Regards
Ahammad Riyaz
--------------------------------------------------------------------------------
If this post helps answer your question, please click on “Accept as Solution” to help other members find it more quickly. If you thought this post was helpful, please give it a Thumbs Up.

Was this reply helpful? Yes No
HellitonWoo 39 on at

Like (1)

Report

I'm also facing the same issue!

My walk-around is to replace the decimal value by the source value.
Simply replace the "number with decimal" with "number without decimal" from the JSON string.

One thing I noticed is that we can't use ".0" in the "Text to find" field, as it is automatically "corrected" to "0.0".

In editing:
After saving:

Was this reply helpful? Yes No
orkan 6 on at

Like (0)

Report

Hi,
Have you find any solution for this problem ? I can't make also the http request successfully due to this reason.

Was this reply helpful? Yes No
MichaelSchweer1 9 on at

Like (0)

Report

Still not fixed. It's been more than 2 years since the initial bug report.

@HellitonWoo workaround is your best bet. Unless your JSON contains ".0" in other places.

Was this reply helpful? Yes No