How to check if value is null with new condition parameters

[Anonymous]

Before Flow was updated to allow multiple condition parameters, I could put something like the following inside a condition:

@(not(empty(items('Apply_to_each')?['PHONE'])))

How do I do this in the current paradigm?

Phone is not empty.

[RobElliott]

In the condition try adding an expression of PHONE is not equal to null. For the right hand box, click in it and go over to the right, select the Expression tab and type null and then select it to put it in the box.

Rob
Los Gallardos

[Anonymous · Accepted solution]

---

@RobElliott wrote:

In the condition try adding an expression of PHONE is not equal to null. For the right hand box, click in it and go over to the right, select the Expression tab and type null and then select it to put it in the box.

Rob
Los Gallardos

---

Thanks for your input, Rob.  I should have given a bit more context.  My data source is a group of Visual Foxpro .dbf tables which I'm accessing through a SQL linked server.  In the data, these string values return from the SQL connector as empty strings rather than null.

Edit:  I've figured out how to do what I originally intended.  Using length is effective, but to me empty() is a bit cleaner and should also cover an unforseen null condition.  

empty(items('ForEachRow')?['CELLPHONE'])

I've decided to handle this by checking if the length of the string is greater than zero. That is working well, but I miss the advanced mode under the conditions.

length(items('ForEachRow')?['PHONE'])

[Anonymous]

Rob, I'm currently trying to resolve a similar issue.  I have condition that is checking if a variable is not NULL.  For some reason it keeps taking the "not null" track even though it's null.  I even set up a test flow that simply sets a variable to NULL, then uses a condition to check.  It keeps choosing 'not null'.  If you have any more advice I would appreciate it.  Thanks

[shavora]

Any idea of how to write expressions? Like a reference guide... I want to use the correct syntax and structure it right, but unsure of how to actually do it. 

[ScottShearer]

@shavora 

Here is a link to the expressions reference

A quick search on YouTube will uncover a bunch of videos on getting started with expressions.

[shavora]

Thanks @ScottShearer I am trying to use the reference guide. I am trying to use the concat function in realtime workflow and every time I structure it like in the reference guide, all I am getting is the actual code as a string instead of the field data I want to fetch. 

These are examples of what I have tried in the standard value slot, I don't find another place to write the concat function in. 

As per this post (https://powerusers.microsoft.com/t5/Microsoft-Dataverse/Auto-populate-the-Primary-Name-column-with-t...), it is supposed to work to use concat in the realtime workflows.

[Raviteja1992]

Its working using is not equal to null

[fstorm]

Excellent.  Thanks Rob.

[DeadFishEddie]

thank you

empty worked for me.

[ldjohnson62]

This is what I used.  I had a Http request for a item from a list.  Then, used Parse Json to pull the fields.  AND, yes.. one of them could be null.   I tried the empty expression and always get a false reading.  Thanks RobElliott for this reply.  Now I move on down the flow.