Answered

Attachment Field empty Parse JSON failed

(1) Share

Report

Posted on by GMorley

Hi,

I've seen a few responses to how to update the Parse JSon code to get Flow to bypass it if the field is left blank, but I've not seen anything that explained explicitly where they update code goes.

In my case, I'm trying to bypass an attachment upload field. If anyone could help me bypass Parse JSON when the field "Attach Terms" is left blank I will be very grateful.

the Schema is as follows:

{

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

]

}

Screenshot 2022-05-09 143440.png

Categories:

Building flows

I have the same question (0)

All responses (10)

Answers (1)

DamoBird365 8,942 Microsoft Employee on at

Like (1)

Report

Hi @GMorley

You can use the filter array action (where the field is not empty) and then run your apply to each on this filtered array.

As the filtered array does not contain your blank attachment key, it would not be in the array.

Damien

Was this reply helpful? Yes No
GMorley 31 on at

Like (1)

Report

Hi, Thanks for responding,

Since it's the Parse that's failing, I assume I need to filter before the Parse, not before the Apply to each? The flow isn't getting as far as apply to each.

I'm assuming From should be the Form response ID, and name is the Attach Terms field?

I know I'm asking you to spell it out for me, but this is my first time exploring what flow can do. Thank you for your help.

Was this reply helpful? Yes No
GMorley 31 on at

Like (1)

Report

@DamoBird365,

I've had a go but I don't really understand what I'm trying to acheive with the filter.

I thought it was a case of checking the form response for attachements and if it does not contain blank then proceed with the Parse.

But if it doesn't do the Parse because the field was blank, it also wont proceed to send the emails. I want it to send the emails whether or not there is an attachment. I just don't want the flow to fail because a file wasn't attached.

I suppose i could put the emails parallel to the Parse JSON so that the attachments don't effect the emails but the flow will still fail at Parse JSON.

Was this reply helpful? Yes No
SPOLHE-C 17 on at

Like (2)

Report

If you're happy with the flow otherwise, you can adjust the JSON directly to accept a null. In your code sample, where it says "type": "string", change that to
"type": ["string","null"]
(do the same with "type": "integer" but NOT "type": "array").

...I'll look forward to a more elegant solution in the replies. (Edited to fix a typo.)

Was this reply helpful? Yes No
Verified answer

eliotcole 4,363 Moderator on at

Like (2)

Report
Hi, @GMorley , if I've understood you correctly, the code goes in the Schema. You essentially tell the Schema that it's OK to set a blank value, and not fail the input.

I'll dig it out, but I may have mentioned it on here at some point, too.

Ah, basically what @SPOLHE-C said ... except the array bracket goes teh other side of the field name.

So, I couldn't see AttachTerms in your schema, so I've used "id" as the field that might be without data, I would set that up in the schema like so:
{ "type": "array", "items": { "type": "object", "properties": { "name": { "type": "string" }, "link": { "type": "string" }, "id": { "type": ["string", "null"] }, "type": {}, "size": { "type": "integer" }, "referenceId": { "type": "string" }, "driveId": { "type": "string" }, "status": { "type": "integer" }, "uploadSessionUrl": {} }, "required": [ "name", "link", "id", "type", "size", "referenceId", "driveId", "status", "uploadSessionUrl" ] } }

Was this reply helpful? Yes No
SPOLHE-C 17 on at

Like (2)

Report

Yes, that! (Can't even blame my system, entirely my error when typing.) Thanks for the quick fix.

Was this reply helpful? Yes No
eliotcole 4,363 Moderator on at

Like (1)

Report

Honestly no bigs! I hadn't realised you had also posted, so I just swerved around you a bit ;-). Frankly I was just thankful that you had, as it meant I could type it all up a bit quicker! 😅

Also, @GMorley , if you want the whole thing to carry on if the input is nil, then you can use a 'Run after' on the following flow action to ensure that it runs whether or not the JSON parser does its thing. Just make sure that your following actions are capable of dealing with a lack of information there. 😉

However, I think deeper interactions would require a bit more of your flow up here.

Was this reply helpful? Yes No
GMorley 31 on at

Like (2)

Report

@eliotcole , @SPOLHE-C thank you for this. I've updated the schema and the flow now works.

Really appreciate the support.

Was this reply helpful? Yes No
dominique2001 11 on at

Like (1)

Report

Hi, @eliotcole I I have the same problem as the person who asked this question. I used the code you provided but it did not work for me. Please see my the code below and the error message it gave me:

Error message : 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 ''.'.

Note: The flow succeeded with attachment but when there is not upload of document, it fails as seen below

{

"type": "array",

"items": {

"type": "object",

"properties": {

"name": {

"type": "string"

},

"link": {

"type": "string"

},

"id": {

"type": [

"string",

"null"

]

},

"type": {},

"size": {

"type": "integer"

},

"referenceId": {

"type": "string"

},

"driveId": {

"type": "string"

},

"status": {

"type": "integer"

},

"uploadSessionUrl": {}

},

"required": [

"name",

"link",

"id",

"type",

"size",

"referenceId",

"driveId",

"status",

"uploadSessionUrl"

]

}

}

Please help if you can. I have been trying to fix this for couple of days now. Thank you

Was this reply helpful? Yes No
eliotcole 4,363 Moderator on at

Like (1)

Report

Hi, @dominique2001, the problem that you have (sorry) is that you're using Parse JSON ... it will *only* react based on the Schema that you give it ... and it can break if what is feeding that doesn't exactly match, or does things that you haven't accounted for.

I would say that you are probably experienced enough (now) to start directly referencing the body or outputs of an action using the body()?['fieldName'] or outputs()?['body/fieldName'] referencing the fieldnames as you want them.

If you wish to work these out, then use the outputs from a test run to find them, and reference accordingly, or have an test action which runs after the one that you want to get an idea of the fields, and push it out that way.

---

Otherwise, my suggestion would be to raise a new question in the forum, including what you have below. :)

Was this reply helpful? Yes No