Parsed JSON contains data, but values are blank when called in flow

(1) Share

Report

Posted on by teespolyglot

104

I have a flow sending an HTTP request to MS Graph api:

which works fine and gets a response with an access token, as expected. I then parse the body of the HTTP and the JSON output contains the expected data.

When i then try to use the outputs of the Parse JSON, however, all the values are blank:

I don't understand how this can be, and I've exhausted every avenue i can think of to try and extract the data. Any help would be appreciated

Categories:

Building flows

I have the same question (0)

All responses (12)

Answers (1)

Mira Ghaly 11,413 Moderator on at

Like (0)

Report

@teespolyglot

Can you send the expression of the failed compose data operation?

Was this reply helpful? Yes No
teespolyglot 104 on at

Like (0)

Report
Apologies, the second screenshot I posted was not the output of the flow in the first screenshot. The flow I showed in the first screenshot, where the input of Compose is

{ "inputs": "@body('Parse_JSON_2')?['body']?['access_token']", "metadata": { "operationMetadataId": "b1cf826e-4194-40c9-a31f-551c7522b4f8" } }

results in the following, where the Compose operation is successful, but the input and output are empty

Many thanks for your assistance! 🙂

Was this reply helpful? Yes No
Mira Ghaly 11,413 Moderator on at

Like (0)

Report

@teespolyglot

Are you sure it is Empty? Have you clicked on Download

Can you send me the output of the HTTP request so I can replicate at my end?

Was this reply helpful? Yes No
teespolyglot 104 on at

Like (1)

Report

Yes, I'm 100% sure. I've tried outputting to compose, setting it as a variable, referencing the parsed json directly, and clicking download for either input or output opens about:blank in the browser

I've sent you the http output by DM. Thanks for your help

Was this reply helpful? Yes No
Mira Ghaly 11,413 Moderator on at

Like (0)

Report
@teespolyglot

I could get the access token directly like below

Schema I used for the ParseJson

{ "type": "object", "properties": { "statusCode": { "type": "integer" }, "headers": { "type": "object", "properties": { "Pragma": { "type": "string" }, "Strict-Transport-Security": { "type": "string" }, "X-Content-Type-Options": { "type": "string" }, "x-ms-request-id": { "type": "string" }, "x-ms-ests-server": { "type": "string" }, "X-XSS-Protection": { "type": "string" }, "Cache-Control": { "type": "string" }, "P3P": { "type": "string" }, "Set-Cookie": { "type": "string" }, "Date": { "type": "string" }, "Content-Length": { "type": "string" }, "Content-Type": { "type": "string" }, "Expires": { "type": "string" } } }, "body": { "type": "object", "properties": { "token_type": { "type": "string" }, "scope": { "type": "string" }, "expires_in": { "type": "string" }, "ext_expires_in": { "type": "string" }, "expires_on": { "type": "string" }, "not_before": { "type": "string" }, "resource": { "type": "string" }, "access_token": { "type": "string" }, "refresh_token": { "type": "string" } } } } }

Was this reply helpful? Yes No
Mira Ghaly 11,413 Moderator on at

Like (0)

Report

@teespolyglot

Please check below

This is returning value for me

Was this reply helpful? Yes No
teespolyglot 104 on at

Like (0)

Report

I could also get the access token. The problem is that even though the JSON has values, when i use the JSON output, the values are empty. The following uses the same schema and compose:

Was this reply helpful? Yes No
Mira Ghaly 11,413 Moderator on at

Like (0)

Report

@teespolyglot

That's pretty weird I have replicated the same and it is showing the value correctly

Was this reply helpful? Yes No
Verified answer

teespolyglot 104 on at

Like (3)

Report
After searching extensively, i solved the issue by amending the schema for the parse json action to:

{ "type": "object", "properties": { "token_type": { "type": "string" }, "scope": { "type": "string" }, "expires_in": { "type": "string" }, "ext_expires_in": { "type": "string" }, "expires_on": { "type": "string" }, "not_before": { "type": "string" }, "resource": { "type": "string" }, "access_token": { "type": "string" }, "refresh_token": { "type": "string" } } }

For anyone else who encounters this error, I realised this must be due to an error in the JSON schema and I ultimately found the correct schema by following the below process:

Parse JSON with HTTP body as input
Initialize variable, type: Object, taking the body of Parse JSON as the input
Second Parse JSON action, taking the variable as input, and using the output body from the first Parse JSON action as a payload for the schema
Compose action using the access token item from the second Parse JSON as input (to verify that the schema used in the second Parse JSON works).
If the compose action produces a result in testing, the schema used for the second Parse JSON action can be pasted into the first Parse JSON, and subsequently the initialise variable, second parse json and compose action can all be removed, and simply use the access token that should now be generated successfully by the first Parse JSON 🙂

Was this reply helpful? Yes No
365-Assist 2,324 Moderator on at

Like (0)

Report
@teespolyglot I had the same issue and your response was really helpful.

Here is my Flow design for anyone else who has this issue:

In my case I was looking for the value of Response in the Body of the HTTP response:

My Compose Action is:

"inputs": "@body('Parse_JSON')?['response']"

---------------------------------------------------
Please Accept as Solution if it solves your question. Or just give it a Thumbs Up if it is helpful as can help others.

Subscribe: https://www.youtube.com/channel/UCFpvUlpx84FuIPOdInGKMTw
Twitter: https://twitter.com/assist_365

Regards
Darren Lutchner - 365 Assist

Was this reply helpful? Yes No