cancel
Showing results for 
Search instead for 
Did you mean: 

SharePoint trigger When an existing item/file is modified

You need to re-add the "When an existing item is modified" and "When an existing file is modified". It was replaced by "Created or Modified" and that is not sufficient. There are cases where certain logic is only executed on creation, and other logic only on modification. Now, don't get me wrong, created and/or modified running the same logic also has uses!

 

With only having the trigger "created or modified" and wanting only certain logic to run on a modification, I have to add logic to ignore creations. You're making more work for your users and taking away basic functionality.

Status: Under Review

Hi everyone, thank you for the feedback, and apologies about the frustration you are feeling.

 

To clarify, we never had a "When an item/file is modified" trigger. It was called that, but the behavior was the same as what we have today. So we merely renamed it to reflect what it was doing, as it was causing a different kind of frustration.

 

The best way to identify item modified remains checking for the difference between created and modified timestamps to be "close enough". Most of the time these will be the same. However, things get out of sync when a large file is being uploaded, where the library item will get created, and then the file upload will complete and change the timestamp. Similarly, when creating a list item, first the item will be created, and then you will have modified events when each attachment completes uploading.

 

We will review how we can make this experience better, but it is a little challenging due to the reasons I tried to explain, so it will not be a quick fix that will be coming in a few weeks.

Comments
Anonymous
Not applicable

Agree - particulary because I don't want to waste Flow runs on an event that I'm only going to terminate via the Flow.  I only want my Flow to take action if a file (properites) was modified, not when it's first created.

Level: Powered On

 If I could, I'd vote 10,000,000 times on this one. I just spent 15 minutes trying to understand why I didn't have a trigger that has been screen captured in a bunch of solution suggestions in the last year and was exactly what I was looking for! 

Level: Powered On

Guys,

 

I absolutely agree with you....

 

Of course we need the action/trigger "When a list item is modified"... 

 

In my case, there are some seconds difference between "created" and "modified" fields.

Power Apps Staff
Status changed to: Under Review

Hi everyone, thank you for the feedback, and apologies about the frustration you are feeling.

 

To clarify, we never had a "When an item/file is modified" trigger. It was called that, but the behavior was the same as what we have today. So we merely renamed it to reflect what it was doing, as it was causing a different kind of frustration.

 

The best way to identify item modified remains checking for the difference between created and modified timestamps to be "close enough". Most of the time these will be the same. However, things get out of sync when a large file is being uploaded, where the library item will get created, and then the file upload will complete and change the timestamp. Similarly, when creating a list item, first the item will be created, and then you will have modified events when each attachment completes uploading.

 

We will review how we can make this experience better, but it is a little challenging due to the reasons I tried to explain, so it will not be a quick fix that will be coming in a few weeks.

Level: Power Up

Thanks for the update, and I understand the issue.

 

How about you leave it up to us. Was thinking if you created 2 triggers timestamp change and size change. we could if we wanted use the timestamp one by itself or combine it with size change one, which should indicate a real change. I appreciate it is possible to update a document and keep the same size, but its unlikely.

 

Dave

Level: Powered On

Here is a suggestion. I don't know what the code behind the scenes of a Flow connector looks like. I don't know if it is event driven or what kinds of classes or structs or pieces of data exist in there, but hear me out please. Is there any kind of information in there about what kind of event fired off the trigger? Could we perhaps have access to some kind of property on the connector that is like a "Trigger Type" field or something that we could check with a branch statement in our flow? Something akin to this pseudocode:

 

If (triggerType = TriggerType.Modified)

  Do rest of flow.

 

I'm also not sure if I buy that the behaviour has always been like this. With the current "Item created or modified" trigger, the flow will run when an item is created AND when any item is modified in the list. There is a myriad of forum posts out there about this trigger and how people have had to create new workarounds since the change from "modified" to "modified or created". Workarounds they did NOT have to have in place when it was just a "modified" trigger. Are you suggesting they were mistaken? With all due respect I find that hard to believe.

Level: Powered On

We have had the option "start workflow when an item has changed" all the way back to early SharePoint Designer days. So I'm sure there's some "signal" in SharePoint that can be used as a trigger in Flow the same way? What is the list item alert triggering on? Can you use that "signal"?

 

I totally understand that there are exceptions, like creating a list item and then attaching files to it. But 90% of the times we just use a basic list, or a basic document library. I think most of use are totally ok with having a trigger that does not work for items with attachments since that's an old and bad way of building things anyway.

Level: Powered On

Another quick solution would be that the version of a document can be used in the Flow. So you can easily create a condition that specifies that a certain action should not be taken when the version is = 1.0

 

Is there any progress on this issue in general? I understand that these things take time but i am in need of a stable solution in this situation.

 

Kr

Level: Power Up

Are we any closer to getting this functionality back?  I had created flows only a few weeks ago that were triggered by modification only - before the trigger was renamed to "create or modify".  Please provide an update on the status.

Level: Powered On

@MichaelDK That's not a bad idea actually. I'm not sure if you can get the Version column info with Flow, though.