Forum Discussion
Documentation on how to create and debug a remote event receiver and attach it to existing list
john john, things have moved on in the last 3 years and the modern approach to setting actions that take place when an item is created or modified in a SharePoint list is to use Microsoft Flow which has now been around for 2 years. You have connectors to over 250 Microsoft Office and non-Microsoft apps, a huge range of actions that you can perform, it handles conditions, parallel branching and approvals, you've got variables, a large range of expressions and so much more.
So, for example, you'd have a SharePoint trigger of "When an item is created or modified" for a particular list, and the following action could be "start and wait for an approval" which sends an approval request to an approver who approves or rejects and adds comments right in their email without needing to go into SharePoint. Then the SharePoint item is updated with the decision, who made it, the date and any comments from the approver. You could then have a condition that if the decision was Approve an email is sent to the person who added the new item, but if it's Reject then a different email is sent.
That's a simple (it takes less than 15 minutes to build) but very common example of how Flow is used every day to automate repetitive tasks and add business logic. It's a brilliant app and I recommend you investigate it.
Rob
Los Gallardos
Microsoft Flow Community Super User
RobElliott wrote:john john, things have moved on in the last 3 years and the modern approach to setting actions that take place when an item is created or modified in a SharePoint list is to use Microsoft Flow which has now been around for 2 years. You have connectors to over 250 Microsoft Office and non-Microsoft apps, a huge range of actions that you can perform, it handles conditions, parallel branching and approvals, you've got variables, a large range of expressions and so much more.
So, for example, you'd have a SharePoint trigger of "When an item is created or modified" for a particular list, and the following action could be "start and wait for an approval" which sends an approval request to an approver who approves or rejects and adds comments right in their email without needing to go into SharePoint. Then the SharePoint item is updated with the decision, who made it, the date and any comments from the approver. You could then have a condition that if the decision was Approve an email is sent to the person who added the new item, but if it's Reject then a different email is sent.
That's a simple (it takes less than 15 minutes to build) but very common example of how Flow is used every day to automate repetitive tasks and add business logic. It's a brilliant app and I recommend you investigate it.
Rob
Los Gallardos
Microsoft Flow Community Super User
RobElliottthanks for the reply. i already know about Flow but have not use it before.. but this is the first time i hear that Flow will be a replacement for RER... as in the on-premises case we did not view Microsoft workflows as a replacement for server-side Remote event receivers.. also i am not sure if flow will allow handling events such as Adding/Editing.. As you described a scenario which is supported by Flow out of the box, let me share a scenario which i use to do inside SP on-premises using server side ER:- Now before adding/editing an item i will check if the user who is performing the action is inside certain sharepoint group (a sharepoint group equal a field in the item which is been added/edited) >> if the user exists i will proceed with the add/edit >> if the user does not exists i will cancel the operation.. i have many scenarios like these to implement custom permissions, and now i want to migrate them to sharepoint online, so the way i am viewing this, is that i will migrate my Adding/Editing server-side ER to be Adding/editing Remote ER,, not sure if flow can help us in this case.
Thanks in advance for your help.