Flow fails on empty optional fields

[Julien2]

Hello everyone!

I have created a flow for a mobile app to trigger the user’s location, the current time based on “checked in/checked out” values, and I have added 3 optional fields to type the client’s name, file content, and comments.
When they submit, a new item will be created in SharePoint list.
The flow fails when they keep the client name, file content, comments empty. It is not necessary to make these fields required because it is an option that on “checked in” the user might not add remarks and maybe he might add some information. However on “checked out” they most probably will.

Here are screenshots of the failing flow:

So how can I deal with this issue if the fields are empty ? Any help would be appreciated.

Thank you!

[yashag2255 · Accepted solution]

Hey @Julien2 

I have recently published a blog on how to overcome exactly issues like this over here. Please take a look and check if that resolves your issue. 

https://www.bythedevs.com/post/how-to-pass-a-null-value-as-an-input-while-using-a-manual-trigger-in-...

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[Julien2]

@yashag2255 

Thanks it's good variety of information in this blog.
I tried also checking for null values by using the null expression.

[yashag2255]

Hey @Julien2 

You will not have to check the value for null if you have the '?' in the expression form as mentioned in my blog. Else, this might fail as the input property is readable only when the user provides an input or else that key is not present and it will make the flow to fail. Makes sense? 

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[Julien2]

@yashag2255 

Thank you for sharing this helpful blog!

[GDSI]

Your blog does NOT address the fact that the Flow is absolutely IGNORING the fact that the parameter is set to optional. 

Create an instant Cloud Flow. Add a parameter. Set that parameter to Optional.

Create another instant Cloud Flow. Add a Run Child to the first Flow. Don't supply the parameter. 

The Run Child call fails with an error like, "Server did not receive a response."

WHY MICROSOFT, WHY?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!