Update Item - Remove Data

[tbrock_troc]

Hi.

I am trying to improve upon a recently built flow which updates a Team List with an asset tag # from an Asset Management List when a team member is assigned to the asset on the Asset Management List. In addition to updating the Team List with the asset tag #, I would like the flow to also remove the asset tag # from the Team List when a team member is unassigned from an asset on the Asset Management List.

I am using Microsoft Lists, if that matters.

• Asset Management List
  • Contains look-up columns to bring in Title, Team Member Name and Team Member Email from Team List
• Team List

Here is the flow as it stands which appears to have worked in terms of updating Team List with asset tag # when a team member is assigned to the asset on the Asset Management List:

• Trigger - item on Asset Management List is created or modified
• Get Info - Team List
  • ODATA Filter - Title eq 'Owner Position' (Owner Position is dynamic content from Asset Management List)
• Condition - length(outputs('Get_items')?['body/value']) = 0
  • If yes, do nothing
  • If no, update iPad Asset Tag column on Team List with Asset Tag # value from Asset Management List

Since the iPad Asset Tag column in the Team List is a single line text-type column, I was under the impression that I could use the Null Expression to effectively remove existing data. Perhaps I am over-simplifying it, but I figured we would need to update the "If Yes" condition to update the field with the Null expression:

• Condition - length(outputs('Get_items')?['body/value']) = 0
  • If yes, update iPad Asset Tag column on the Team List with null value (blank)
  • If no, update iPad Asset Tag column on Team List with Asset Tag # value from Asset Management List

When I remove a team member from the Asset Management List, the flow successfully executes through the "Yes" condition path however nothing appears to happen on the Team List and the field remains populated:

Any assistance is appreciated!

[takolota]

I think you messed this up

• Trigger 2: @not(equals(triggerOutputs()?['CurrentOwner'], triggerOutputs()?['OwnerPosition_x0028_Text_x0029_']))

CurrentOwner does not look like it is the corresponding column to OwnerPosition Test. Where is the original Owner Position column?

And if you want it to still trigger when the original column is null…

Removing Assignment - Owner Position is null but Owner Position2 still has data

• Flow does not appear to trigger at all

Then you will need to remove the trigger condition of @not(equal(…., null))

[tbrock_troc]

Thanks again.

@not(equals(triggerOutputs()?['Owner_Position'], triggerOutputs()?['Owner_Position2']))

In the expression you had provided, should that first Owner Position in bold be Owner Postion2 as well?

[tbrock_troc]

Got it - I think I do want it to trigger if I "unassign" and Owner Position (original) becomes null as that would be the trigger to remove the asset tag from the team list, I think?

Thanks again for all of your help.

[takolota]

No. It’s supposed to check if the original Owner Position column is not equal to the copy of the Owner Position column.
When someone updates the item to unassign someone, the 1st flow still has who was previously assigned in the copy column so you can identify & update the right item in your alternate list.

Then this second flow should identify that the original Owner Position column is null, while the copy Owner Position column is still set to the previous owner, so they are in fact not equal & the flow should run to update the copy column with the value from the original column.

[tbrock_troc]

Gotcha - sorry, I hadn't updated the thread with the corrected condtional expression once I caught that I was missing the "0" and "body/" portions of the reference:

@not(equals(triggerOutputs()?['body/CurrentOwner0'], triggerOutputs()?['body/OwnerPosition_x0028_Text_x0029_']))

[tbrock_troc]

That appeared to be it.

When assigned, the flow ran correctly. When I unassigned, the flow was triggered and ran successfully however I ended up with an empty array again.

It looks like I may want to add the condition after the trigger back so that I can prevent it from writing over Owner Position2 with a blank.

Aside from that, I think the only other issue I need to test for is if it triggers itself in a loop still.

[tbrock_troc]

It looks like the added condition had the desired effect.

I have also confirmed that there is something with the assigning portion of the flow that causes the flow to loop and re-trigger itself.

[takolota]

Yes, if re-assignments is all you are using this for, then you may want to add the same trigger condition to the 1st flow to prevent it going off if the Position & Position copy column are already the same. That should also help prevent runs if people often make other unrelated edits in that list.