Power Automate Parse JSON error. Invalid type. Expected Object but got Array

(0) Share

Report

Posted on by smorley

546

Hi PA People,

I've been working on a flow from a test list which works fine, and now moving it into production, and I'm getting the error of "Invalid Type, Expected Object but got Array".

I always seem to trip over Parse JSON syntax. The flow runs daily and goes a Get Items action with an oData filter of anniversary date = today.

Next I select the Department Administrator.

I then initialize my array variable with a union statement.

union(body('Select_Department_Administrator'), body('Select_Department_Administrator'))

Next my Parse JSON statement uses the array variable as the content.

The schema is below:

{
"type": "array",
"items": {
"type": "object",
"properties": {
"Claims": {
"type": ["string", "null"]
},
"DisplayName": {
"type": ["string", "null"]
},
"Email": {
"type": ["string", "null"]
},
"Picture": {
"type": ["string", "null"]
},
"Department": {
"type": ["string", "null"]
},
"JobTitle": {
"type": ["string", "null"]
},
"@odata.type": {
"type": ["string", "null"]
}
},
"required": [
"@odata.type",
"Claims",
"DisplayName",
"Email",
"Picture",
"Department",
"JobTitle"
]
}
}

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

Pstork1 68,697 Most Valuable Professional on at

Like (1)

Report
The schema you listed isn't the schema that is showing in the Parse JSON screenshot. Check the schema and you should be fine. The one you list starts

{ "type": "array", "items": {

But the one in the screenshot shows

{ "type": "object", "properties": {

Was this reply helpful? Yes No
smorley 546 on at

Like (0)

Report

Well @Pstork1 I did make it work based on your post. Thanks. Here's the weird thing. My test flow here's the output from the JSON action. This is the one that works.
In the production flow, with the same syntax. It fails.
I swapped out "array" with "object" like you suggested, saved it, and ran it, and it now works fine.
When I go look at it after I've saved, it looks like it did when it failed.
I'm glad you got it to work for me, but I'm a little mystified by it.

Was this reply helpful? Yes No
Pstork1 68,697 Most Valuable Professional on at

Like (0)

Report

Its not just the type array that is different in the production schema. I would copy the whole schema from test, paste it into production and save it. Then test production.

Was this reply helpful? Yes No