{
"type": "ParseJson",
"inputs": {
"content": "@body('Get_response_details')?['r52970a37d7f44534842ce10180188f96']",
"schema": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"link": {
"type": "string"
},
"id": {
"type": "string"
},
"type": {},
"size": {
"type": "integer"
},
"referenceId": {
"type": "string"
},
"driveId": {
"type": "string"
},
"status": {
"type": "integer"
},
"uploadSessionUrl": {}
},
"required": [
"name",
"link",
"id",
"type",
"size",
"referenceId",
"driveId",
"status",
"uploadSessionUrl"
]
}
}
},
"runAfter": {
"Condition": [
"SUCCEEDED"
]
}
}
"name": {
"type": "string"
}
//will fail if "name" is ever missing or null
"name": {
"type": ["string","null"]
}
//will work if "name" is ever missing or null.
Generally though I find that "ParseJSON" is more trouble than it's worth in most cases. It's best to just get a sample JSON body and keep it open in NotePad or something in another window for reference. Then you can use expressions to refernce whatever property you want from your data output. Usining a "?" will cause it to accept nulls if the property is missing from the data on the current run.Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.