Retirement of SharePoint 2010 workflows: Don’t panic!

On 6 July 2020, Microsoft announced the retirement of SharePoint 2010 Workflows within Office 365. This is part of Microsoft’s drive towards encouraging use of Power Automate, part of the Microsoft Power Platform, which lets you connect Microsoft 365 services together (as well as many popular third-party services).

So what does this mean for people still using SharePoint 2010 workflows? Well, from 1 August 2020, no newly-created tenants will have SharePoint 2010 workflows switched on. So, if you had been planning to move any SharePoint 2010 workflows to a new tenant, as of now that won’t be possible.

Clock ticking on SharePoint 2010 workflows

For those who already have SharePoint 2010 workflows created within an existing tenant, you have until 1 November 2020 to recreate these workflows within Power Automate.

From the start of November, Microsoft will begin to remove the ability to run or create new SharePoint 2010 workflows. This suggests that, while you can’t run the existing workflows, they will still be accessible. Exactly for how long, though, we don’t know.

Read more

Share this page

Tech blog: Hooked on Webhooks?

SharePoint now has limited support for Webhooks. Our Technical Lead, Paul McGonigle, explores how they can be used, and whether they’re worth using.

New features get added to SharePoint Online regularly, and I find it’s worth staying on top of them so we can keep our solutions cutting-edge at CompanyNet. One of the new features I’ve been digging into recently is Webhooks. Webhooks are HTTP callbacks that are automatically triggered when something happens. At the moment, support for Webhooks in SharePoint is limited to SharePoint lists.

On first glance, they seemed like they might fill a void in the SharePoint online developer toolset. I took the opportunity to explore Webhooks with a real-world scenario, and found several oddities with working with them.

Read more

Share this page

Remote Site Provisioning with SharePoint Online and PnP

An introduction to the SharePoint Patterns and Practices (PnP) library – discover how how it can be used to power remote site provisioning.

With many organisations now moving, fully or partly, to Office 365, the way solutions are developed is evolving rapidly. In this series of blog posts, I’m going to share some of the more innovative tools available in Office 365, and the support Microsoft offers those who want to work at the cutting edge.

In this post, I’ll look at a very common requirement – SharePoint site provisioning. Site provisioning is the software-assisted creation of SharePoint sites, with certain elements already set based on default values. The business benefits to providing a site provisioning toolset include:

  • Helps prevent site sprawl, ensuring sites are only created when and where they are needed.
  • Users can create sites in a more consistent manner. This includes consistency in Permissions, List, library, and Folder names, Navigation and Metadata.

With an on-premise set-up, developers have multiple options available to them for provisioning new sites – site definitions, web templates, features (with feature receivers), web services, and so on.

Read more

Share this page