Unanswered

Parse JSON 2 Error - Need to allow null value for image upload

(0) Share

Report

Posted on by drmarinko

I have a form that requires uploading a drivers license image (.jpg file) and then a condition is in place for certain members to upload an MVR image. The intention is for the 2nd Upload File to be optional. The Flow fails for any forms that don't upload both images. If both images are uploaded, it works fine. How can I program the 2nd Upload File object to accept Null values? Is there another way to outsmart this by having a default value for the 2nd Upload File or just have it duplicate the 1st Upload File path?

Error:

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

Categories:

Building flows

I have the same question (0)

All responses (8)

Answers (0)

Sort by

Pstork1 69,485 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Do two things.

1) Remove that column from the list of required columns in the schema.

2) Change the Type in the schema from "Type": "Image" to "Type": ["Image", "null"]

Was this reply helpful? Yes No
drmarinko 8 on at

Like (0)

Report
Copy link

Link copied!

Thank you for the fast reply. I am not clear on your first instruction. How do I do this? 1) Remove that column from the list of required columns in the schema.

Was this reply helpful? Yes No
drmarinko 8 on at

Like (0)

Report
Copy link

Link copied!

Below is the Parse JSON 2 in our flow. After the condition in the flow, there is an "Initialize variable (MVR)", then "Parse JSON 2", and then "Apply to each 2". See attached picture.
{
"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": [
"No"
]
}
}

Was this reply helpful? Yes No
Pstork1 69,485 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

You won't need to do #2 since the columns in your required list are already very limited. The only column you list as required is "No". Did you create the schema by hand or by using the sample button?

Was this reply helpful? Yes No
drmarinko 8 on at

Like (0)

Report
Copy link

Link copied!

The schema was done by a Tech that no longer works here, but I think he did a copy/paste from another forum. I am open to suggestion on changing the schema, but I don't claim to understand it well enough to customize for our needs. In the Form, we limit it to 1 file, size limit 100MB, with type Word Excel PPT PDF or Image. The first Upload file object is Required and the 2nd is Not Required. Open to any suggestions on the schema.

Was this reply helpful? Yes No
Matthy79 4,188 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hello,

The schema is not the problem, but if you parse the JSON and the content to parse has no value, you have nothing to parse.

You could check for the null value, but that won’t solve your problem, because I am pretty sure that somewhere after that action, you will need content from the parse json.

So you have to check what is really causing the problem. You normally can’t parse an image by using json parse. So what do you parse here and why is there no data available?

Was this reply helpful? Yes No
drmarinko 8 on at

Like (0)

Report
Copy link

Link copied!

The form has 2 sections for uploading files and works fine when a file is uploaded for each. There are conditions when only 1 file is needed and the 2nd is not. Those conditions are failing since null value for the image upload. Am I supposed to use something other than Parse JSON to upload an image and allow null?

Was this reply helpful? Yes No
Pstork1 69,485 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

I would use sample output from the form details in a run to generate a new schema. Then you can set the fields that may be null to allow either the specific type or null. @Matthy79 is correct that you will then have to take into account that those fields may be null later in your flow. But the schema for the parse JSON is indeed the problem. The only other alternative is to make uploading each of the files required.

Was this reply helpful? Yes No