Update is not null

Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. This is the place for advice and discussions 0 0. Thank you for your fast response, you guide me to the correct answer. Can we alse use Coalesce for this?

How is this correct? Show 1 more comment. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name.

Email Required, but never shown. Yes I checked the executive plan but after that I was Confafed then I was asking for the question. Add a comment. Active Oldest Votes. Those queries won't do the same thing. Improve this answer. DeadlyJesus DeadlyJesus. Deepshikha Deepshikha 2 2 bronze badges. Your way is right, but I do not need this condition right now. Thanks for your answer; — Ashish Patidar.

I think you have a misunderstanding here. I want my flow to update two text fields in my list to be empty if the user modifies a lookup field to make it empty.

In my first list Address Change list I have a lookup field Approved School that references a list of schools and their email addresses in a second list School Email Address. When a user edits an item in Address Change and modifies the Approved School field value, a flow runs to update two other fields in Address Change:.

It also works if I change it from one value to another different value. But it doesn't work when I remove the value from Approved School choose "None" in the lookup. The flow runs, seems to do the "Get Item" without any problems, but when it needs to run the Get Items to pull the email address related to the selected school in this case, empty , it doesn't come back with anything.

In the Get Items output, it shows the body value as a set of square brackets:. And though the Apply to Each action has a checkmark indicating that it ran without an issue, it didn't do the update item step:.

To compensate, I added a condition after the trigger to determine if the Approved School field is populated or not, and then act accordingly:.

I also realized that in my question, my second action Get Item isn't needed - I can retrieve the information from the initial When an Item is Created or Modified action, so I don't need to follow it up with Get Item. The trigger is the same as before, and in the condition I use the length function to determine if the Approved School field is populated:.

Power Automate is warning me that I may be creating the dreaded perpetual loop: my flow is triggered when an item is modified, and as a result it makes a modification which could then trigger the flow to start again. To manage this, I've just added two trigger conditions to my initial When an Item is Created or Modified trigger. The first trigger checks to see if the value the user has just defined for Approved School matches the value that's currently in ApprovedShoolComp which is the reason the ApprovedSchoolComp field exists.

If they haven't changed it, then I don't want to make an update.