Share
Report
63Just want to share a lesson learned on my Power Automate journey!
A user came to me with a flow error message they did not understand. They were using a Condition connector to compare a SharePoint value to an empty field.
Due to data sensitivity, I don't have a screen shot of the exact error but here is a close example:
The thought came across, maybe a recent Microsoft update was made and now blanks in the Condition connector are no longer allowed. After taking a look at this article, Reference guide for expression functions - Azure Logic Apps | Microsoft Learn, I found one of those special Microsoft notes, indicating that with Condition Connectors, null values (null) are converted into empty strings (""), and that the connector behaves differently when you compare with an empty string verses a null value.
At this point I had a hunch that maybe it was not the end of the comparison causing the issue, but the beginning. We tested using Null() verses an Empty Field in the end of the comparison.
Sure enough...you are still able to use nothing in place of the end comparison in the Condition Connector...however...you need to be aware if your SharePoint field selected is Null, not empty strings. When a SharePoint Field is Null, it's not available in the return data (I believe it's in JSON).
Due to this, if you're using it in a Condition connector, you may retrieve an error, unless you account for Null AND Empty Strings.
You can do this by using an OR statement in the Condition Connector and listing both scenarios.
I hope this helps someone along their journey. Happy Friday, Happy Solutioning!
All responses (
Answers (
