cancel
Showing results for 
Search instead for 
Did you mean: 

Disable Event Firing when Flow updates a SharePoint list item

Add a feature that will allow flow to disable event firing when updating a SharePoint list item, so that the Flow doesn't get stuck in a loop. Currently if I create a flow with a SharePoint list trigger when item is created or modified and have the Flow update a field in the item the loop gets stuck in a loop. One workaround is to add logic to check if the field(s) still need to be updated and if not then don't update the item but even in that case the flow will be triggered twice. It just makes sense to have an option that will allow Flow to update an item without triggering an event that will cause the same Flow or another Flow to run against the item again.

Status: Declined

Hi all,

 

After thoroughly reviewing this idea, we have decided not to proceed with this idea for a couple of reasons.

  • SharePoint events are no longer event receiver based and are performed using webhooks or polling where applicable
  • Other Office 365 applications and internal systems like auditing may and will rely on such changes like updates to items, files and other entities in SharePoint

However, that said, we understand the crux of the issue which is to help avoid loops. We will work with the flow team to come up with a generic model/pattern that applies across data source/connections for similar scenarios.

 

Thanks all for your input and please submit/vote your ideas as we are actively monitoring the ideas forum.

 

Thanks,

Chaks

Comments
Level: Powered On

I'm surprised this hasn't been addressed yet...

@darogael - what, in your estimation is the best workaround for this issue (perhaps you could link to it?)? I'm struggling to find an acceptable method

Level: Power Up

Hi Mate,


Thanks a trillion mate!
It works like charm, saved a lot of energy & time.

I’m trying to get an Entitlement Collection running on a NetApp vFiler in 7-mode. The Resource Crawler works fine but the Entitlement Collector fails with the following error in the logfile:

Failed invoking API —> System.Net.WebException: The request was aborted Could not create SSL/TLS secure channel.

 

We have both ssl and tls enabled on the NetApp:

options tls.enable

tls.enable on

 

options ssl

ssl.enable on

ssl.v2.enable on

ssl.v3.enable on


SIQ Entitlement Collector fails on NetApp 7-mode with SSL error?

Anyways great write up, your efforts are much appreciated.
Obrigado,

Naresh

Level 8

@Jeff_Thorpe Thanks!

 

I agree 100%... Everybody's work is a little different but it is not an exaggeration to say that nearly every Flow I want to create currently is affected in this issue in some way.

Level: Powered On

Or maybe indicate on the sharepoint item that it was last modified by Flow, instead of the user name. Then it would be easy to have a condition to see if Flow was updating or user.

Level: Powered On

I agree.

MS Flow needs to run a single instance of each worflow, by default - just like under WF2013.