Flow: Existing item is modified triggers when a new item is created in Sharepoint list

[Alam]

How do I resolve this?

I have two flows and both are being triggered when a new item is created.

[AmayKulkarni]

yes, i am also facing same issue, created and modified are different in Item create, how to handle it?

[wnzn]

Take a look at this blog post. Using this API call does not trigger another instance of the same Flow.

https://robertschouten.com/2018/04/30/update-file-metadata-with-rest-api-using-validateupdatelistite...

[MariaOrza]

@wnzn There is one trigger called : When an existing item is modified  in this Flow Template . Maybe the use got it from there. 

[DanielaHo]

Hi Kris, 

I have tried your solution but when I enter 

@equals(triggerBody()?['Created'], triggerBody()?['Modified'])

I get an error saying "The expression is invalid". Has anything changed since your post?

[wnzn]

You need to add one part of the condition (created) in the left input box and the other part (modified) in the right input box. 🙂 

[marsin04]

FOUND HIDDEN ON MODIFY TRIGGER ACTION - I was also having trouble due to the Created & Modified times being 1 minute apart from one another (even when it truly was a new Item), so I found a Template that claims it Triggers solely on a Modified Existing Item. Use this Template and then change out the subsequent actions (after the Trigger action) to what you need!

[Anonymous]

Still not working. Any suggestions? my flow is constantly looping endlessly. Is there an option to stay execute once and stop afterwards?

[wnzn]

No, as every instance of your Flow is unaware of other runs.

As I suggested, you can update your current item by calling the SharePoint REST API and using the ValidateUpdateListITem() method.

The body of your call should look like this:

{
	"formValues": 
	[
		{"FieldName": "FileLeafRef", "FieldValue": "Rename.docx"},
		{"FieldName": "Title", "FieldValue": "New Title"}
	],
	"bNewDocumentUpdate": true
}

Where you add each field you want to update in the formValues object.

By setting the bNewDocumentUpdate to true, you say to SharePoint that this is a "system update" so there is no new version created and the Flow is not triggered again.

You can find more information about supported fields at the bottom of this post: http://blog.arvosys.com/2018/07/06/list-items-system-update-options-in-sharepoint-online/index.html

[CRISLIPSKI]

I LOVE YOU!!! Works perfectly!

[DanielaHo]

Hi All, 

I am finding that a Flow triggered 'when item is created or modified' takes several minutes to be triggered when the item was modified... whereas the Flow triggers very quickly when a new item was created. Anyone else finding the same thing?