Last week I created a Flow with a condition to check if a field is blank.
The advanced syntax is as such:
This was working for a second, but now it is returning always as True, no matter what.
Can anyone help me? Has anyone built conditions on If Field is Blank??
Solved! Go to Solution.
I am runinng a bit of a SQL sync. A custom SQL table gets the SharePoint List ID value to that we can quickly update the matching rows between the tables periodically. In this flow, I am checking for a value in the SQL List results (SPO ID field (datatype int)) if it's null then I haven't create the row in the SharePoint list yet, so I I will go create it and then update the SQL value with the new row ID. If it has a value, then it already exists and I want to update that row in the SPO list. So the condition works when it's empty, but when it's not it fails because "The template language function empty expects its parameter to be and object, an array, or a string. The provided value is of type integer. Please see blah blah blah." So I need to change the data type or make it a string, that seems pretty hokey...I must be missing something.
Like proper grammar, double negatives are bad in Flow. Do a check for null and if the answer is false then build your decisions down the No path in the condition. This isn't an approval, saying No is not a bad thing.
Have things changed since this last post because this doesn't work for me.
Here's my flow:
I'm essentially trying to do the if field is blank trick. And it ain't working no matter how many tutorials and guides I've read.
My field is in a list in SP. It is blank. I want the flow to send an email if the field is blank and not to if it has something in it.
I have tried the dynamic content way and am now trying the expression way. I first tried:
(a) 'Field' is equal to 'Null' - didn't work
Then I tried the above pictures provided - it won't accept it as you can see from the second picture.
Please help. Hair pulling happening.
Yes have tried that but it's not working, as in it's giving me the 'I don't like 'null' error.
It's a Do Until with the left hand value populated by the list field (not a formula) a condition of 'is not equal to' and the right hand value with the expression 'null'
I've heard that a double negative doesn't work. I have no choice! I cannot put anything into the field by default.
Is there a way to create an expression which gives out a true or false or a yes or no which Flow can valuate on? IF so how?
I´m trying to make a flow that creates an item on a sharepoint list after a Form from Forms is submited, and on that form if a field is empty I wanted the flow to make onething but if it had something it had to do something else.
I tried using the Null expression on the condition (Field > Equal to > Null) and it only worked when the condition was false, in other words only when the field wasn't empty.
So I just didn't put the Null expression and left it empty (Field > Equal to > ) just to try, I never really thought it would work but to my surprise it worked like a charm.
@Pieter_Veenstra Do you know if checking for a people field can be used with null? Source is a sharepoint list but it is failing every time when I try to use the People on the left and the null expression on the right? Thanks!
Join us for the first ever Power Platform Online Conference!
Keep your eyes open for our upcoming T-shirt design contest!
Look out for new contribution recognition badges coming SOON!
We've updated and improved the layout and uploading format of the Power Automate Cookbook!
Fill out a quick form to claim your user group badge now!
Find out where you can attend!