Parse Json error for Attachments

[ParmSandhu]

Im getting an Error for the parse Json for gathering the values of an attachment. i have posted a screenshot below. the flow wont get past the parse json

Parse Json Code:

{

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

        ]

    }

}

[Anonymous]

Hi @ParmSandhu ,

1. try removing  " "type": {}," from the code and check.

Regards,

Chandrashekhar

[ChadVKealey]

Can you provide a screenshot of the error you see in a failed run? A close-up of it (rather than the whole screen) would be best. I honestly can't make anything out in the screenshot you posted; the text is too small and when I zoom in, it gets all pixelated.

[ChadVKealey]

Also, are you certain that you selected a file upload question as the "Content" for the Parse JSON action? That schema only fits with "File upload" questions from a Microsoft Form. 

[ParmSandhu]

Yes it is a file upload question on forms, but it is not required, think that was worth mentioning.

[ParmSandhu]

[ChadVKealey]

If you submit the form and attach/upload a file, does the flow work? If so, this behavior is expected. Basically, if you don't attach/upload a file, the response to that question is empty (null), which doesn't fit the schema that the action is using. If you don't plan to make the file upload required, you can add a condition that evaluates the response to that question and ONLY does the parse json (and other file-related steps) if that response is NOT null.

[ParmSandhu]

Thanks Chad i started realizing that after running a couple of test runs and tried setting a condition. But am having issues with that as well because i am unsure of how to set a condition to tell the process that there is an attachment provided. i have posted another post here:

https://powerusers.microsoft.com/t5/Building-Flows/Condition-Control-in-power-automate-for-Attachmen...

[ParmSandhu]

so i have figured out the conditions and the parse json is passing now but now i am getting stopped at the "Get file meta data" im not sure what is causing this i am using the same steps as the video. here is the error.

[ChadVKealey]

That error means that it can't find the file that you're specifying in the input for the action. Can you provide a screenshot showing the input for the Apply to each loop and the Get file metadata action?

Ensure that the input for Apply to each is the "Body" being output from the "Parse JSON" action.

Also, make sure the input for the Get file metadata action is the "driveId"."id" (the dot/period in between is required!), also being output from the "Parse JSON" action.

[ParmSandhu]

Get file metadata input

{

    "method": "get",

    "path": "/datasets/default/files/b%25219bFCJ9HphUOgKe0yfEWfHubU0Dvw5wBNmvKSd3UNCog5kRNL5WzORLlbWzaSj8e8.014KXUNJEKVCYJ6VJLFNA3X3YDDGR7XQY2",

    "host": {

        "api": {

            "runtimeUrl": "https://flow-apim-msmanaged-na-eastus2-01.azure-apim.net/apim/onedriveforbusiness"

        },

        "connection": {

            "name": "/providers/Microsoft.PowerApps/apis/shared_onedriveforbusiness/connections/shared-onedriveforbu-596ddbfc-814e-4887-9181-5fd2-8bee2210"

        }

    },

    "authentication": {

        "scheme": "Key",

        "parameter": "*sanitized*",

        "type": "Raw"

    }

}

it is the body from the parse json and the driveid is items('Apply_to_each')['driveId'] same with the id. and i do have a period between them.

[ChadVKealey]

Something's not right with that input. Did you manually create the "Apply to each loop" and set the input, or did you add the "Get file metadata" action and select the "driveId" (letting Power Automate create the Apply to each loop) as shown here: https://youtu.be/amByVPsgUw8?t=388? 

[ParmSandhu]

I did “get file meta data” and selected drive id and allowed power automate to create the apply to each loop function. I tried both ways and it still gave me an error.

[ChadVKealey]

OK, I'm not sure where things are going wrong for you, but I recorded a short walk-through showing what the inputs & outputs should look like: https://www.screencast.com/t/wxXM8V4qcy 

[ParmSandhu]

Thank you so much for creating that. so it seems that i get a different input for "Get file metadata". i think its worth noting that i am working off a shared forms and shared power automate, where i am not the original owner. would that have any issues in the matter? the parse JSON passes perfectly now.

Input for get file metadata

{

    "method": "get",

    "path": "/datasets/default/files/b%25219bFCJ9HphUOgKe0yfEWfHubU0Dvw5wBNmvKSd3UNCog5kRNL5WzORLlbWzaSj8e8.014KXUNJEKVCYJ6VJLFNA3X3YDDGR7XQY2",

    "host": {

        "api": {

            "runtimeUrl": "https://flow-apim-msmanaged-na-eastus2-01.azure-apim.net/apim/onedriveforbusiness"

        },

        "connection": {

            "name": "/providers/Microsoft.PowerApps/apis/shared_onedriveforbusiness/connections/shared-onedriveforbu-596ddbfc-814e-4887-9181-5fd2-8bee2210"

        }

    },

    "authentication": {

        "scheme": "Key",

        "parameter": "*sanitized*",

        "type": "Raw"

    }

}

[Michael_Yen]

Referring to PamShandhu post  on ""Get file metadata" error message. I experienced the exact same issue. Which I suspect is due to Shared Forms and Shared Power Automate workflow.

My conclusion was that the "Get file metadata" error will occur if

1. The Form is not originally created by ourselves

2. The Power Automate Flow is not originally created by ourselves

When I used a Form created by myself, and used the Flow described by Chad, the Uploaded file gets into the Email successfully.

If anyone has other solution, please share. Thank you

[ChadVKealey]

@Michael_Yen , to be more specific, a user can only "get file metadata" on files to which they have at least read access. If it's a personal form that you did not create, then those files are saved into the OneDrive of the form's creator and unless they specifically shared the folder where the files are stored with you, then you don't have access. That is, someone might create a personal form and "share" it with you; that gives you access to the form, but not to the OneDrive folder where the form is storing uploaded files. 

Now, if it's a group form, the files are stored in the group's SharePoint site, so any member of the group has access to the form itself as well as the files stored in SharePoint. 

Regarding creation/ownership of the flow...it's a more complicated situation. Really, it's about the connections used in the flow and what access they have to OneDrive, SharePoint, etc.

My examples assume that either it's a personal form and the flow is being created by (and run in the context of) the form's creator OR it's a group form and the flow is being created by (and run in the context of) a member of the group that owns the form. If you are sharing a form (personal or group) or sharing a flow, your results and experiences may vary.

[Michael_Yen]

Hi Chad

Thank you for your explanation.

It made sense.

When I guided my colleague who is the Owner of the Form to create the Flow, the File upload and email was triggered successfully.

I will see if  when she shares her OneDrive Folder containing the Form File Uploads, the original flow will work.

Best regards

[SepPowProf]

I face the same issue. As a form collaborator, I am editing a shared flow to retrieve file metadata from a Shared Form and faces error. Manage to resolve it simply by getting the form/flow owner to allow my profile access to his/her OneDrive folder of that specific Shared Form. Test the flow and it works perfectly.

[WesleyM2]

I added the condition and it worked to bypass JSON file upload. Thanks, now I just have to figure out how to get multiple files to upload instead of just the first one.