Checking if an Item is Updated or Modified

[Anonymous]

Flows has some serious issues.

I have two lists. List A and List B.

I have a Choice option on List A that specifies three choices: Send to List B, Other, Misc.

What I Want to Happen

1. If a User creates a new Item in List A, and selects the Send to List B Choice, and presses Save - The Item should be added to List B

2. If a User modifies an Item in List A, and the Send to List B Choice is selected upon Save - The respective item in List B should be updated.

What is Actually Happening

1. This works perfectly.

2. When a user modifies an Item in List A that exists in List B, the Item is not getting updated. Instead Microsoft Flows decides that this is all of a sudden a new item and decides to add it to List B again with the exact same information. I think it is adding the same item and assigning it a seperate Internal ID.

When I go to see the history of the flow runs I am hilariously getting a "Bad Gateway" error which is misleading because that is obviously not the issue.

For some reason the referential integrity of the Item is failing. It is not able to associate my Item in List A with List B on an update even know I specified it in the flow.

The Error Message That Makes no Sense  (Note: I have removed Client IDs for security reasons)

{
  "error": {
    "code": 502,
    "message": "BadGateway",
    "innerError": {
      "status": 500,
      "message": "Item does not exist. It may have been deleted by another user.\r\nclient
    }
  }
}

My Flow

Is flows really this broken? Why was this product released in this state? This is absurd.

[v-yuazh-msft · Accepted solution]

Hi @Anonymous,

Please modify the flow in your third image as screenshot below:

Best regards,

Alice

[Anonymous · Accepted solution]

@v-yuazh-msft This is not the solution. Notice that I renamed my Title column to Project ID so your logic would never work.

It looks like the underlying issue is renaming the Title Column in Lists.

You all should really do some Unit Testing concerning the referential integrity of renaming the Title column and then using it in flow logic in Lists.

With that being said, if I renamed my Project ID column back to its original default ugly name that makes no sense, Title , then your solution works.

Though it baffles me that the User has to first in flow logic, run a Apply Each case to each item in the list in a loop, this logic should be behind the scenes, I shouldn't have to "Get Items". The whole process is convoluted for simply Updating an Item in a seperate List.