Hello @TimRob
There seems to be a issue with your schema. I tested a small sample on my side with the picture you provided. I used:
{
"value": [
{
"OrgsId": "1234567890-0987654321",
"FriendlyName": "Communication Engineering",
"UniqueName": "org123456",
"State": 1
}
]
}
As my body for the parse JSON and also used the same JSON for generating the Schema within the Parse JSON action. When generating the schema from sample I got this:
{
"type": "object",
"properties": {
"value": {
"type": "array",
"items": {
"type": "object",
"properties": {
"OrgsId": {
"type": "string"
},
"FriendlyName": {
"type": "string"
},
"UniqueName": {
"type": "string"
},
"State": {
"type": "integer"
}
},
"required": [
"OrgsId",
"FriendlyName",
"UniqueName",
"State"
]
}
}
}
}
Which looks very different from your schema. Another test I ran was I wanted to see if I could get the Dynamic content from the Parse JSON using a Compose action.
Since the Body JSON provided is an array, indicated by:
"value": [
When selecting the dynamic content for any of the values, flow automatically puts everything in a loop.
This makes me believe that your schema is the root cause of the null values.
To fix:
- You can copy the entire body from the Parse JSON action you provided above. And paste it in the Parse JSON 'generate from sample' button. This should correct the schema
or if this still does not work.
Could you provide the full details from the Parse JSON body and or the body of the Kusto action. (You can change the values and give dummy data if you need)
