cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Helper V
Helper V

Flow Condition "if field is blank" always returning false

Hi all, 

I'm trying to have a Flow check if a field is empty. I used the syntax: @not(empty(triggerBody()?['MyField'])) found in this thread:

https://powerusers.microsoft.com/t5/2017-Flow-Forum-Holiday-Haul/Check-if-sharepoint-field-is-not-bl...

 

But no matter what the condition returns false. 

 

Same with this syntax: @Empty(body('Get_file_properites')['MyField']) found in this thread:

https://powerusers.microsoft.com/t5/General-Flow-Discussion/Check-if-a-field-is-blank-in-SharePoint/...

My whole Flow is like this:

 

Flow1.PNG 

Where If Yes an approval process is started, and If No, an email is sent. 

No matter what, the condition runs as false. 

 

Any advice?

Sylvie

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Helper V
Helper V

Re: Flow Condition "if field is blank" always returning false

Looks like @Pieter_Veenstra already answered this question for me ages ago and I blanked it all out. Probably trying to forget my traumatic experiences. 

He answers it here: https://powerusers.microsoft.com/t5/Building-Flows/Flow-Condition-If-Field-is-Blank/m-p/136853#M1354...

Solution is:

 

Using Basic Mode, set your field and then use Expression Null in the value field on the right. 

Seems like advanced mode just doesn't work. 


Thanks Pieter (again)

View solution in original post

9 REPLIES 9
Highlighted
Helper V
Helper V

Re: Flow Condition "if field is blank" always returning false

Update:

I changed the field from a hyperlink to a single line of text field. 

The Flow now runs both actions after the condition. 

 

So it starts an approval process AND it sends an email. Which is bizarre.

Highlighted
Helper V
Helper V

Re: Flow Condition "if field is blank" always returning false

Solved. 

 

For whatever reason, those syntaxes weren't working. 

This one did: 

 

@Empty(item()?['MyField'])

Highlighted
Helper V
Helper V

Re: Flow Condition "if field is blank" always returning false

Update: this condition is no longer working. 

 

Now it is only returning as true. 

With the syntax  @Empty(item()?['PublishedVersion'])  it is returning True whether PublishedVersion is empty or not. 

 

Help?

Highlighted
Frequent Visitor

Re: Flow Condition "if field is blank" always returning false

Any updates on this? I am currently having the same issue. Always True.

Highlighted
Helper V
Helper V

Re: Flow Condition "if field is blank" always returning false

Looks like @Pieter_Veenstra already answered this question for me ages ago and I blanked it all out. Probably trying to forget my traumatic experiences. 

He answers it here: https://powerusers.microsoft.com/t5/Building-Flows/Flow-Condition-If-Field-is-Blank/m-p/136853#M1354...

Solution is:

 

Using Basic Mode, set your field and then use Expression Null in the value field on the right. 

Seems like advanced mode just doesn't work. 


Thanks Pieter (again)

View solution in original post

Highlighted
Advocate I
Advocate I

Re: Flow Condition "if field is blank" always returning false

Amazingly I can't get "null" to work for me now. It even pops up in the suggester box but when I click it it says "invalid expression". I did get your initial suggestion (@Empty(item()?['MyField'])) to work though! 

Highlighted
Frequent Visitor

Re: Flow Condition "if field is blank" always returning false

For some reason, the null method does not work for me. I have an Assigned To (people/group column) that breaks my flow if no name is entered, so I am adding a condition to auto assign if null. Unfortunately, the condition always returns False. 

 

condition.png

 
Highlighted
Regular Visitor

Re: Flow Condition "if field is blank" always returning false

Check for Null works fine for me (Release April 2020).

Highlighted
Frequent Visitor

Re: Flow Condition "if field is blank" always returning false

I tested it on a new flow and it still did not work for me. There seems to be a decent variation of functionality between users on forums when it comes to the person/group columns. I wonder if there is something different with company profiles that causes this?

 

Fortunately, I am no longer relying on the person/group field. I chose to create an array variable with user emails, append my different scenarios, remove any duplicates and convert to a "claims" field format. So far, this has been working wonderfully for me.

 

Best regards,

Alex

Helpful resources

Announcements
firstImage

Super User Program Update

Three Super User rank tiers have been launched!

firstImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

firstImage

Join the new Power Virtual Agents Community!

We are excited to announce the launch of Power Virtual Agents Community. Check it out now!

firstImage

New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

Top Solution Authors
Top Kudoed Authors
Users online (7,272)