JSON parsing error expected number but got string

[RampalsT]

I have an App that contains a button that submits all my fields to a Power automate flow that creates an item in a SharePoint list with that information.
The item creation works well, but after the item creation i try to respond to Power Apps and return the ID of the created item.

In my flow runs it says that it went well and returned a number, but in Power Apps i'm trying to assign that number to a Context Variable and it shows the JSON parsing error and assign something to my variable.

I tried Creating the flow again with new connection references and change the returned value to string ( When i did this i found that if i call my variable id, it returns something like this: /workflows/b235092357903252/runs/3532532, and in my monitor the response body shows properties, id (this is the value that i get if i call my var id and put as a string in my flow), name and type, i don't know if there is expected to show something else)

This is my var code:

Thanks in advance

[enriqueglopez]

Is your response a Text type? Or Number type?

Anyway, you can parse the String to Number in your PowerApp, using the Value() function.

Set(ItemId, Value(YourFlow.Run(params...).itemid);

Or

Set(ItemIdString, YourFlow.Run(params...).itemid);
Set(ItemId, Value(ItemIdString));

If this post helps, then please consider Accept it as the solution to help the other members find it.

[RampalsT]

I proved that as well, but it simply gets my variable in blank like the picture i posted before.

[enriqueglopez]

Is your original response variable in Blank too? Maybe you have a typo, your code must be something like this:

Set(ItemId, Value(YourFlow.Run(params...).itemid); 

Or

Set(ItemIdString, YourFlow.Run(params...).itemid);
Set(ItemId, Value(ItemIdString));

Important to have exactly the same variable written in Power Apps than in Power Automate (itemid).

If this post helps, then please consider Accept it as the solution to help the other members find it.

[RampalsT]

Still nothing, i put the last .itemid that i didn't had before, but the variable value that Power Apps recives is a blank value.

My flow runs correctly, but the variable is not received in Power apps.

[enriqueglopez]

@RampalsT 

Your response output is called 'Body', and inside has a JSON Object.

Try this:

Set(ItemIdString, YourFlow.Run(params...).body);

ItemIdString should have {"itemid": "41"} inside.

The next step is work with JSON functions to map the response and get the property itemid. 

My suggestion, to make this easier, if you are only returning that single value (itemid), modify your Respond to PowerApp or flow as follows, where yourvariable is the thing you return as itemid:

If you do that, my first example in this thread should work.

---------------------------------------------------------------------------------------------
If this post helps please consider Accept it as the solution to help other members to find it.

Have a great day!

[RampalsT]

It seems the problem is different. If i see how Power Apps receives the information form the Power Automate response, the value is not received, or at least  didn't see it in the response JSON. 

"response": {
        "startTime": "2024-01-08T07:28:38.5593674Z",
        "correlation": {},
        "status": "Waiting"
      }
    },
    "id": "/workflows/x/runs/y",
    "name": "name",
    "type": "Microsoft.Logic/workflows/runs"
  },
  "responseType": "json"

 The response action should return something else i think, right? 

I proved all the cases that you send me, and its the same always, Power Automate sends the response, but Power Apps don't receives it. 

[enriqueglopez]

Did you refresh your flow in Power Apps when you added the response action? 

[RampalsT]

Yes, every time that i modified something i clicked on refresh. 

[RampalsT · Accepted solution]

I found the solution, my Power automate flow had Concurrency Control on and it turns on the Asynchronous Response and its what it make Power Apps don't wait for the flow response. I had to create my flow again and set my concurrency control off, and that enables the option to set the Asynchronous Response off.

Simply go to configuration in your respond to a PowerApp or flow action and turn the Asynchronous Response off.