Do You need event receivers in MS flow?
With MS Flow adding more actions and triggers, there is almost no need to create Event Receivers anymore. But one significant feature which Event Receivers offered was to disable the event firing when we are updating the same list item with the event receiver.
Which is an example of remote event receiver?
In this example, moment an item is added to the Feedback list another new item gets created and it continues in an infinite loop as the RER gets activated on ItemAdded event. This is just an example and in real life, a lot of different business requirements can be accomplished using RER.
When did SharePoint start using remote event receivers?
Remote Event Receivers were introduced along with SharePoint 2013 and the arrival of the App model. Microsoft provided tooling with Visual Studio to create Remote Event Receivers, but unfortunately the only way to expose this tooling was in the context of a Provider-Hosted App.
How to avoid endless recursive calls in MS flow?
If an MS Flow with an ‘Item is created or modified’ trigger tries to update the same list item, it re-triggers itself. This article shows a workaround on how to avoid the endless recursive calls. MS Flow is one of the key Apps on Office 365, which helps in quickly automating tasks and easily build complex business logic on list item level events.
How to stop MS flow from re-triggering?
But one significant feature which Event Receivers offered was to disable the event firing when we are updating the same list item with the event receiver. But MS Flow doesn’t provide the provision to stop a trigger. Consider the below example where we have a list with 3 columns.
How does MS flow trigger when an item is created?
A simple flow can be configured which triggers whenever an item is created or modified, which will update ColumnSum with a sum of ColumnOne and ColumnTwo. The MS Flow steps may look like below. This Flow keeps triggering itself infinitely, because of the ‘Update Item’ action.