Answered

JSON Data Collected but Not Used

(0) Share

Report

Posted on by SalamiPi3

After an agent passes a string to this flow, the flow parses the string as a JSON object. After reviewing the run, the string is successfully parsed as a JSON and is verified. However, when the json attribute is called it fails. I am receiving the attribute with:

body('Parse_JSON')?['itemName']

If anyone has any idea, I would appreciate it.

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Expiscornovus 33,891 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @SalamiPi3,

Can your payload return more than one item? Otherwise it might still return it as an item in a collection. In that case you need to tell it which item (even though it is only returning 1 item).

In that case your expression might need to be:

first(body('Parse_JSON'))?['itemName']

Additionally, can you share a screenshot with the JSON payload you are trying to parse. This will also help troubleshooting.

Happy to help out 😁

I share more #PowerAutomate and #SharePointOnline content on my Blog, LinkedIn, Bluesky profile or Youtube Channel

Was this reply helpful? Yes No
SalamiPi3 17 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Expiscornovus,

The payload consists of 12 items. An agent passes a string into the flow,

Which is then parsed as a JSON

Here is one of the test runs parse:

Was this reply helpful? Yes No
Verified answer

Expiscornovus 33,891 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @SalamiPi3,

I see the property is called "Item Name" and not "itemName" in the raw outputs of the parse json action. So it might just have been a small typo in your first attempt?

And it is not an array, but just an object. So try the below instead, without the first function.

body('Parse_JSON')?['Item Name']

Happy to help out 😁

I share more #PowerAutomate and #SharePointOnline content on my Blog, LinkedIn, Bluesky profile or Youtube Channel

Was this reply helpful? Yes No
SalamiPi3 17 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @Expiscornovus,

That was correct! Although it is odd - I put in exactly what power automate had provided as the output from the parse. It automatically set it as that, maybe due to the naming convention? Despite that, the JSON had in fact taken all variables that had multiple words and separated them with a space. Adding a space to all variables when being processed worked!

Thank you!

Was this reply helpful? Yes No