Handling NULL in Parse JSON

[ChrisCC]

I have an API which has the following characteristics:

Schema:

{
  "type": "array",
  "items": {
    "type": "object",
    "properties": {
      "StartDate": {
        "type": "string"
      },
      "EndDate: {
        "type": "string"
      },

    }

  }
}

**************************

Example failure payload:

{
      "StartDate": "6/15/2017",
      "EndDate": null,
 }

Note that this works if both StartDate and EndDate are not null

The Parse JSON step with the above schema returns "Error - Expected String, received null"

Replacing the EndDate data type "string" with "any" causes it to be unreadable in following steps (as though it was never parsed) and changing it to "data" causes an internal server error.

Is there any way to create a schema which allows null values in the "Parse JSON" step?

[v-micsh-msft]

Hi @ChrisCC,

I don't think there would be schema which could allow Null value.

Please consider replace the Null value with some string, or add a condition to check if the value is Null with the empty funciton.

Or you may consider submit this as an idea, to suggest add the Null support under parse JSON action.

Regards,

Michael

[JoeGasper · Accepted solution]

This seems to be working:

"heat_index_f": {
"type": ["number","null"]
},
"heat_index_c": {
"type": ["number","null"]
},

https://powerusers.microsoft.com/t5/Building-Flows/parse-JSON-Ignoring-null-value-s-when-parsing-JSO...

[TobyJH]

Works for any data type:

"id_numeric": {

"type": [

"integer",

"null"

]

},

"department_head_name": {

"type": [

"string",

"null"

]

},

[SwJ23]

I used this suggestion for a few flows and it works great, but it prevents me from using Dynamic content from any Parse JSON action whose schema I modify to accept null values. 

After a great deal of dinking around I stumbled across removing the "type": "string" field altogether, leaving in its place a null object. Other than needing to be very careful with where you put the typeless dynamic content, I haven't encountered a serious drawback yet; but that doesn't mean there isn't one!

Your schema:

"heat_index_f": {},
"heat_index_c": {}

OP Schema:

{
  "type": "array",
  "items": {
    "type": "object",
    "properties": {
      "StartDate": {},
      "EndDate: {},

    }

  }
}

[testasdfasfsafa]

I can't believe after all these years that Microsoft still hasn't fix this simple issue