Handling null values in conditional trigger

(0) Share

Report

Posted on by CU01081947-0

716

Hello Power Automate Community,

I hope you can help please.

I'm using the "Common Data Service (Current Environment)" connector. I want the Flow to run when:

An "Opportunity" is marked as "Close Won"

And

The "Opportunity" field "Originating Lead" is populated.

I'm doing this using a"Conditional Trigger" and it's working great, so long as a value is populated in the "Opportunity" field "Originating Lead". See below:

Trigger condition.png

But if that's not populated I get a failed message.

The next step in the Flow after the trigger is to get the Originating Lead GUID. So I used the "Get Record" action. But I receive the below error because the Opportunity didn't have a value in it's Originating Lead field.

Error on Lead action.png

I read somewhere that I should use the "coalesce", and I read information about that at this URL https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/functions/function-isblank-isempty but I just can't write the expression needed to substitute the below expression using coalesce.

@not(equals(triggerBody()?['originatingleadid_value'],'null'))

Any ideas on how to do that please? I believe the problem is the 'null' value, as that's a string and it's looking for an integer.

Thanks in advance to anyone that can help, I've wasted many hours trying to solve this.

Garry

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (1)

Verified answer

Community Power Pla... on at

Like (0)

Report

Hello @GarryPope

You could do it as a filter array then use the below within advanced:

@or(equals(triggerBody()?['statecode'],1),not(empty(triggerBody()?['originateleadid_value']))

Hope this helps.

Thanks

Bradley

Was this reply helpful? Yes No
CU01081947-0 716 on at

Like (0)

Report

Hello @Anonymous,
Thanks so much for the feedback, I really appreciate it.
Just so I'm clear, the expression you gave me is for the Trigger Condition right?
If so, I removed the two expressions I had in there and used your expression. Unfortunately I'm getting an error, sorry. See below:

I actually think my original request is not possible. In Dynamics when I create an Opportunity and don't add a value in the Originating Lead field, when I look at the Trigger output that field is not in there, which, I believe, is to be expected. To solve this, after the trigger I'm just going to add a "Condition" to then check if a value is in the "Originating Lead" field or not.

I did this before, but was trying to be clever and reduce my flow from running when not needed.

Thanks anyway for your help,

Garry

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hello @GarryPope

Apologies, I misread you initial issue - I was suggesting that you used a filter array with my expression.

This would have allowed you to narrow down the output to only the required values.

Thanks

Bradley

Was this reply helpful? Yes No
CU01081947-0 716 on at

Like (0)

Report

Hello @Anonymous,
No problem at all. It was probably the way I wrote it! I appreciate your help. The Condition I added after the trigger is working a treat.
Thanks very much,
Garry

Was this reply helpful? Yes No