cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
AbleAmazing
Frequent Visitor

Trouble expressing a null value in a Dataverse lookup column on a condition branch

Hello Team,

 

I have the following actions in a relatively simple flow:

AbleAmazing_0-1670610587716.png

 

I'm trying to create a conditional branch on a contact (value) lookup column in Dataverse. If the column is null, do one thing. If it is not null, do the other. Unfortunately, I can't seem to find the right way to express a null value for this data type in a condition. I have tried expressing the null value as follows:

  • null as a text string
  • null as an expression
  • "" as a text string

I have also tried using empty expression:

 

 

 

empty(outputs('Get_Case')?['body/_primarycontactid_value']) is equal to true​

 

 

Nothing has worked. The flow continues to process as if the value is null each time even when it's not or just return an error. I have noticed that when the value actually is null in Dataverse, the column itself doesn't seem to be included in the raw output of the row I'm retrieving in the previous action--which doesn't make sense to me. I would expect that column to be included in the raw output whether it the value is null or not. I'm not limiting the columns in the Get row by ID action.

 

Any assistance is appreciated.

1 ACCEPTED SOLUTION

Accepted Solutions

Hi @AbleAmazing 

 

Ignore the above and I tried the below and worked.

 

image.png

 

Add a compose above the IF condition and map the value of the lookup, then check the run history.

 

Thanks



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

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials

View solution in original post

3 REPLIES 3
abm
Super User
Super User

Try the below under the IF condition equal 0

 

length(outputs('Get_Case')?['body/_primarycontactid_value')) 



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

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials

Hi @AbleAmazing 

 

Ignore the above and I tried the below and worked.

 

image.png

 

Add a compose above the IF condition and map the value of the lookup, then check the run history.

 

Thanks



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

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog
Power Automate Video Tutorials
AbleAmazing
Frequent Visitor

Thanks. Turns out I spent four hours being very stupid and didn't realize that our case table surfaces two separate contact columns in Power Automate and I was calling the wrong one.

Helpful resources

Announcements
Power Automate News & Announcements

Power Automate News & Announcements

Keep up to date with current events and community announcements in the Power Automate community.

Community Calls Conversations

Community Calls Conversations

A great place where you can stay up to date with community calls and interact with the speakers.

Power Automate Community Blog

Power Automate Community Blog

Check out the latest Community Blog from the community!

Top Solution Authors
Top Kudoed Authors
Users online (4,496)