SharePoint new item and modified item triggers fire at new item.

[Anonymous]

I have two seperate Flows.

One is when a new item is created:

Another one is complex logic when an existing item is modified:

When a new item is added to the SharePoint list both flows trigger and are executed. However it should only be the "When a new item is created" that triggers.

Users rarely manually add items to this SharePoint lists. The list has a PowerApp where new items are added and modifications are done to the list.

[v-monli-msft · Accepted solution]

Hi @Anonymous,

I have reproduced this issue. When I add a new item in the same sharepoint list, both "when a new item is created" and "when an exsiting item is modified" triggers will have a run. I will try to report this issue to the product team and will notice you once I got any update later.

Regards,

Mona

[gamoraes]

Hi @Anonymous and @v-monli-msft.

Here we found this issue too, we workaround with a condition in modified flow verifying if the Created field is not equals Modified field, if this condition is false the flow start. This work well for us

Best Regards,

Gustavo Moraes

[manlamcheng]

I tried this, it didn't work becuase there is 0.4 second difference between created and modified in my situation

[psi]

@v-monli-msft Are you really marking this as Solved?  I don't consider the work around presented to be an actual long term solution.

It has been over a month since this was reported, when can we expect a fix to be rolled out?

[v-monli-msft]

Hi @psi,

So it’s by weird design that “when an item is modified” triggers when a new item is added. We will very soon be renaming the “When an item is modified” to “When an item is created or modified”. Sorry about the confusion this has caused.

Regards,

Mona

[pnthrzrule]

But wait - wait - wait!

I want to have a separate flow for when an item is modified to send out an approval email. Why are we combining the two. BTW...it's already been renamed.

[jakekemme]

I agree, Inserts and Updates are completely different actions, and just like a database, should NOT be linked together as a generic 'stuff happened' action.

[v-monli-msft]

Hi @jakekemme@pnthrzrule,

I do agree with you. Please consider to post an idea in Flow idea forum:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

Regards,

Mona Li

[dsmith]

Does this affect all current flows that initially just used the 'When an item is updated or modified' trigger? I now cannot update all of my flows based on that trigger. The dynamic content does not populate any of my SharePoint list items.