Solved: Re: What happened to the conditions in FLOW?

joef · ‎02-07-2019

HI All,

What happened to the complex conditions in FLOW?

All I have now is the basic with an add button to add more basic conditions!

I create flows for when items are created or modified.

I use a condition where modified = created for new items. (And of course I have to convert to my timezone)

then I use complex conditions where I test for empty columns to send send out update alerts.

I can have 5 or more alerts sent in one FLOW.

--New items go to a group

--updated items go to another group when some column is updated

--updated items go to other groups based on other updated columns. ...

I tried to use the new basic "where sent to is not equal to" and I left the criteria blank, but that didnt work. it sent even when the column was blank.

then I tried where not equal to '' also failed like leaving empty!

Can someone please tell me how to do the below in the new basic condition?

@and(not(empty(triggerBody()?['DateSent'])),not(empty(triggerBody()?['DateSentToTax'])),empty(triggerBody()?['DateSentTo']),empty(triggerBody()?['DateReviewedByTaxDept']))

Thanks,

Joe

faustocapellanj · ‎02-07-2019

Hi @joef

I went over the announcement made by the Flow team yesterday about the new Condition builder, and in it, they explain how to build a complex condition to check if values are empty, etc. Here's how I tested the new approach on my end:

When you start a Condition, you only have one row, so to add more, click on Add > Add row. Since your condition contains an AND, this will be the default option above the condition rows.
Now, by looking at the expression in your post, it's checking if the first 2 fields are not empty AND if the last 2 fields are empty.
To achieve that, you first build the expression in the Expressions tab for the value to check as follows:
```
empty(triggerBody()?['DateSent'])
```
For the logical operator, select is not equal to, and the value on the right, go to the Expressions tab again and type true. You can continue the same approach for the remaining fields the condition needs to check. Here's a screenshot of my final condition with the same fields used in your expression:
Here's the link to the announcement: https://flow.microsoft.com/en-us/blog/build-more-powerful-conditions-in-flows-and-more/

I hope these instructions point you in the right direction. Please, do not hesitate to reach out if you have any questions.

Regards,

Fausto Capellan, Jr

Fausto Capellan, Jr
Did I answer your question? Mark my post as a solution! Did my response help? Please give it a thumbs up!

View solution in original post

faustocapellanj · ‎02-07-2019

Hi @joef

I went over the announcement made by the Flow team yesterday about the new Condition builder, and in it, they explain how to build a complex condition to check if values are empty, etc. Here's how I tested the new approach on my end:

When you start a Condition, you only have one row, so to add more, click on Add > Add row. Since your condition contains an AND, this will be the default option above the condition rows.
Now, by looking at the expression in your post, it's checking if the first 2 fields are not empty AND if the last 2 fields are empty.
To achieve that, you first build the expression in the Expressions tab for the value to check as follows:
```
empty(triggerBody()?['DateSent'])
```
For the logical operator, select is not equal to, and the value on the right, go to the Expressions tab again and type true. You can continue the same approach for the remaining fields the condition needs to check. Here's a screenshot of my final condition with the same fields used in your expression:
Here's the link to the announcement: https://flow.microsoft.com/en-us/blog/build-more-powerful-conditions-in-flows-and-more/

I hope these instructions point you in the right direction. Please, do not hesitate to reach out if you have any questions.

Regards,

Fausto Capellan, Jr

Fausto Capellan, Jr
Did I answer your question? Mark my post as a solution! Did my response help? Please give it a thumbs up!

AlanPs1 · ‎02-07-2019

Please check here or here for a solution.

"Enter your expression on the left side of the row. Then, select Equals to and enter true."

So what used to be:

Has now become:

If helpful, please mark with thumbs up.

Thanks, Alan

Did I answer your question? Mark my post as a solution!

Proud to be a Flownaut!

joef · ‎02-08-2019

Hi @faustocapellanj,

Thank you!! I didn't see the announcement about the change.

faustocapellanj · ‎02-08-2019

You're welcome!!!

Fausto Capellan, Jr
Did I answer your question? Mark my post as a solution! Did my response help? Please give it a thumbs up!

LarryAlx · ‎09-24-2019

Need some help. None of these suggestions are working for me.

expression I'm usingNot allowing to continue flow

faustocapellanj · ‎09-24-2019

Hi @LarryAlx

What happens if you add that Condition below the Query for Salesforce Records? The Condition should check outside the Apply to each loop you have there. Question: what's in value the Apply to each is looping through?

Thanks!!!

Fausto Capellan, Jr
Did I answer your question? Mark my post as a solution! Did my response help? Please give it a thumbs up!

LarryAlx · ‎09-26-2019

@faustocapellanj ,

I really appreciate your response and after I posted my question, I spent the whole evening trying to figure it out and finally got it working. I believe I actually ended up doing exactly what you said. I was checking the body within an apply to each, when I took it out, things started flowing.

FlowingIt's Working!!!