Microsoft
MicrosoftHi Grant, we're finalizing the new digest template, and it should be available for you to try out in the next 2-3 weeks. You can see the Power Automate trigger under the SharePoint connector as "Recurring digest of updates (preview)". Right now, it only includes new files/items & updates to existing files/items. Delete events are available in Power Automate but requires additional site admin permissions so we haven't included that in the catalog of workflows templates just yet.
Hi Nate Tennant. Thanks for your reply. Looking forward to seeing it in action. I'm still expecting it to fall short though - will it include details of all the version history changes over that time and what metadata was changed, etc.? We get this with SharePoint Alerts which should be treated as a baseline.
However, there are still so many core issues with the Power Automate approach, one of which you just highlighted.
The only viable option I see is a massive update to SharePoint Rules that cater for everything we had before in SharePoint Alerts. But I'm not seeing Microsoft are looking to do this unfortunately, and think Power Automate is the way to go - which it absolutely isn't.
I can address bullet point #2 above. I'm currently adding Alerts lists to SharePoint Online sites that require alerts, and then modifying Power Automate to read from the lists. End-users can add/remove themselves from the lists. Of course, this requires much more effort than the old SharePoint alerts required.
As for the user leaving the business, we use a dedicated account to build flows. Then the flow can be shared with other people. I have been trying to tell as many people as possible not to build a flow that runs under your account and is not shared. Ideally an account created for this purpose should be used.
The other bullets points, especially regarding deletions, are absolutely valid. I look forward to a better solution for this from Microsoft.
Hi KCRyan37. Thanks for your reply. Unfortunately, we are managing 65k+ users across 130k+ SharePoint sites in a large global company. Users need to be able to manage and build alerts themselves as they were able to do before. Also, all the flows being created by users (which is easy to do now in a list or library via the menu) will all be created in the Default Power Platform environment, outside solutions, running under the users account, zero visibility with other users, Users moving roles or leaving the company causes major issues in these instances, etc.
For some context, we have some Project Managers (PM) that have alerts across hundreds of Project libraries (daily and weekly summaries across create, update, delete). This is just a few clicks per library with SharePoint alerts. Having to build hundreds of flows just for a single PM is a massive undertaking, and still no option for delete). Multipy this by the entirety of our complex environment, and quickly becomes unmanageable with the proposed solutions by Microsoft.
We don't see Power Automate as a viable option at scale to replace what worked extremely well - even for users with just Read access.
