We bring you a special one-hour episode of AskSympraxis due to Microsoft’s recent blog post from Chris McNulty and support article about ending support for SharePoint 2010 workflows in SharePoint Online.
SharePoint 2010 workflows could be created in SharePoint Designer, as could SharePoint 2013 workflows. SharePoint 2010 workflows also underlie the out-of-the-box classic workflows. The Microsoft announcement is about both SharePoint 2010 and 2013 workflows, but the schedule for each is different.
We wanted to clarify a few points in the recording. There are multiple HTTP related actions. Send an HTTP request to SharePoint is a free connector and allows you to make a request to the SharePoint REST API. There is also an HTTP action that allows you to make an HTTP request to any endpoint. This is a premium connector. In the video, we talked about calling child flows. This would require using the HTTP action and would be a premium feature.
Flows are no longer calculated using pooled calls. We said that it was 5000 calls per account per month. This is incorrect. Flows are not calculated that way anymore. Instead, there are limited by the number of API calls/day. Different plans provide different numbers of calls.
Thanks to John Liu for pointing out these errors.
Resources and Takeaways
- Todd’s Blog Series on Workflows: https://symp.info/tkworkflow
- Microsoft Workflows to Power Automate: https://aka.ms/sp-workflows-guidance
- Ask Sympraxis Workflow Infographic: https://symp.info/workflow
- John Liu’s SharePoint Workflow to Power Automate: http://johnliu.net/blog/ninja-list-the-great-migration-of-sharepoint-workflow-to-power-automate