cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
yoshihirok
Memorable Member
Memorable Member

Error: Parse JSON "The request content was invalid and could not be deserialized"

1.png

 

 

How can I fix the Error "The request content was invalid and could not be deserialized" of "Parse JSON" action ?

 

Error:

The request content was invalid and could not be deserialized: 'Error converting value "ParseJson" to type 'System.Nullable`1[Microsoft.Azure.Flow.Templates.Schema.FlowTemplateOperationType]'. Path 'properties.definition.actions.Parse_JSON.type', line 1, position 190.'.   "

 

Json data:

{ "address": { "streetAddress": "21 2nd Street", "city": "New York" }, "phoneNumber": [ { "location": "home", "code": 44 } ] }
 
Json schema:
{
  "type": "object",
  "properties": {
    "address": {
      "type": "object",
      "properties": {
        "streetAddress": {
          "type": "string"
        },
        "city": {
          "type": "string"
        }
      }
    },
    "phoneNumber": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "location": {
            "type": "string"
          },
          "code": {
            "type": "number"
          }
        },
        "required": [
          "location",
          "code"
        ]
      }
    }
  }
}
 
This schema generate from JSON data by "Use sample payload to generate schema"
 
Regards,
Yoshihiro Kawabata
 
2 ACCEPTED SOLUTIONS

Accepted Solutions

Hi Yoshihiro,

 

I have seen a similar thread reporting this issue, the thread link is:
https://powerusers.microsoft.com/t5/Flow-Forum/Error-from-Parse-JSON-step-when-Updating-Flow/m-p/214...

 

Staff Mark has replied the thread, and we know currently there is an issue on Parse Json action and it is being fixed now, seems it would be fixed soon.


Thanks for your patience and understanding.

 

Best regards,
Mabel Mao

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

Hi Yoshihiro,

 

Mabel is correct. This is a new action, and the issue isn't with parsing JSON, but rather with our service even knowing the JSON parser action even exists. I've validated that this works in our test environments. You should see the fix roll out this week, barring any unforeseen issues.

 

Best,

 

Mark

View solution in original post

9 REPLIES 9
v-yamao-msft
Community Support
Community Support

Hi Yoshihiro,


I found a documentation about “Open API Specification (fka Swagger RESTful API Documentation Specification)”, please check this link for a reference:
http://swagger.io/specification/


Please feel free reply if you need more help.

 

Best regards,
Mabel Mao

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi @v-yamao-msft

 

Are there any json data and the schema, without error ?

I cannot find json data and schema which can save flow without error.

 

Regards,

Yoshihiro Kawabata

Hi Yoshihiro,

 

I have found several Jason file examples, could you try with these Jason file examples to see if you would still get the error in the flow?
Please check the following link for more details:
https://www.sitepoint.com/10-example-json-files/
https://adobe.github.io/Spry/samples/data_region/JSONDataSetSample.html

 

Best regards,
Mabel Mao

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi @v-yamao-msft, thank you json example.

 

I re-check a json, and a schema, but still error at create flow.

 

json:

{ "color": "red"}

 

schema:

{
  "type": "object",
  "properties": {
    "color": {
      "type": "string"
    }
  }
}

 

error still be happend.

 

Regards,

Yoshihiro Kawabata

Hi Yoshihiro,

 

I have seen a similar thread reporting this issue, the thread link is:
https://powerusers.microsoft.com/t5/Flow-Forum/Error-from-Parse-JSON-step-when-Updating-Flow/m-p/214...

 

Staff Mark has replied the thread, and we know currently there is an issue on Parse Json action and it is being fixed now, seems it would be fixed soon.


Thanks for your patience and understanding.

 

Best regards,
Mabel Mao

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

Hi Yoshihiro,

 

Mabel is correct. This is a new action, and the issue isn't with parsing JSON, but rather with our service even knowing the JSON parser action even exists. I've validated that this works in our test environments. You should see the fix roll out this week, barring any unforeseen issues.

 

Best,

 

Mark

View solution in original post

Hi, @masisley, @v-yamao-msft

 

Thank you for your reply.

I'm waiting "the fix roll out this week".

 

Regards,

Yoshihiro Kawabata

 

 

Hi @masisley, @v-yamao-msft Thank you fix this issue.

 

Now 2/24/2017 JST, I can use "Parse JSON" without error.

 

Regards,

Yoshihiro Kawabata

MK1
Helper IV
Helper IV

Hi,

 

Is this error fixed.

I'm only facing this issue with couple of items not for all.

Not, sure how to fix when issue is with few items in the list.

 

Any ideas would help.

 

Thanks,

MK1

Helpful resources

Announcements
MPA_User Group Leader_768x460.jpg

Manage your user group events

Check out the News & Announcements to learn more.

V3_PVA CAmpaign Carousel.png

Community Challenge - Giveaways!

Participate in the Power Virtual Agents Community Challenge

Carousel 2021 Release Wave 2 Plan 768x460.jpg

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

R2 (Green) 768 x 460px.png

Microsoft Dynamics 365 & Power Platform User Professionals

DynamicsCon is a FREE, 4 half-day virtual learning experience for 11,000+ Microsoft Business Application users and professionals.

Users online (896)