Parse_JSON Error: InvalidTemplate. Unable to process template language expressions in action 'Parse_JSON' inputs at line '0' and column '0': 'Required property 'content' expects a value but got null. Path ''.'.

[BGreen2]

Hello all,

I am new to Power Automate and am trying to transfer Form responses with an attachment to a Microsoft List.  In my flow I have a Parse_JSON step that is erroring out.  The following message is included with the error: "InvalidTemplate. Unable to process template language expressions in action 'Parse_JSON' inputs at line '0' and column '0': 'Required property 'content' expects a value but got null. Path ''.'."

In other posts where I have seen this error pop up, it looks like it was due to a particular response of the form not containing an attachment.  I have required the attachment step on the Microsoft Form so that a response can not be submitted if it does not have an attachment submitted.  In the tests I have run, an attachment has always been included.  When creating the Parse_JSON Schema I copied the file location as it appeared in the "Get Response Details" step and used that as the "Generate from Sample".

I am not sure where I am going wrong.  Any help or suggestions would be greatly appreciated.  Below is my Parse_JSON Schema in case it is needed.  Thank you so much for any help that can be provided!

{

    "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"

        ]

    }

}

[v-bofeng-msft]

Hi @BGreen2 ,

Could you please show me your flow?

Best Regards,

Bof

[BGreen2]

Hello, sure thing!  Thank you for looking at this.

[Tanveer]

I am also having the same issue, could not resolve, i tested the flow when i setup and always attached an attachment but without attachments this is the first error in production.

Any help would much appreciated

[tansleypete]

I am getting this error as well. For me i think it must be that it is expecting an attachment but there isn’t one. Is there a way for the flow to carry on past this even if there is no attachment?

[niki1]

I have the same error. Is there a solution to this?

[BGreen2]

Hello All,

I ended up creating a new flow with the exact same information/set up.  When I re-created the new flow, the problem disappeared and the flow worked.  I am not sure if there might have been a strange typo/small mistake on the previous flow that I just could not find or if something else was going on, but for whatever reason the new flow worked.  I would recommend creating a new flow if you are experiencing this issue to see if that helps resolve the issue.

Thank you!

[Craig_Cowley]

Hello,

Has anyone been able to resolve this please? I've created two flows using this and thought they were working, until someone tested without an attachment.

Thanks
Craig

[niki1]

Hello, 

I used the Try, Catch and Finally blocks and Scope using the video at https://www.youtube.com/watch?v=f9Sf5TUA6aQ and it works in both options w/wo attachments.

[Craig_Cowley]

@niki1 Thanks for the link, I'll have a look.

I did manage to get a workaround, by adding a condition of 'Document Upload' is equal to "", if false, the Parse JSON etc was applied.

[slarson77]

Same issue.

It used to work, in January.  Now I get this error.  Nothing has been changed or updated in my flow, so I know it's not me because it used to work.

[mukaruernest]

Looks like there is a property called 'Content' that is not on your Parse_JSON Schema.