How to solve the most common issues on SharePoint Designer

If you work with SharePoint at this point you’ve probably realized that SharePoint Designer is one of your best allies but still is a bit temperamental and sometimes it just refuses to work properly.

In this article, I’ll cover the most common issues and how to fix them.

Fix SPD issues


Fix publishing pages with custom page layouts created from template

This article is a continuation of my previous article that explains how to save publishing sites as templates.

Per the feedback received some people was not able to access the sites created with the template, this happens with sites that include pages with custom page layouts.

Before getting into details about how to fix this please notice that the previous article is a hack to save the site as a template, save site as a template is disabled in all Publishing sites and other type of sites with publishing features active, this means that the hack may not work in all SharePoint scenarios.

Page layout template error


How to fix 401 error after applying a custom master page to SharePoint

This is a short article but it can save you precious time when you apply a custom banding to your SharePoint site.

After applying a custom master page to the site some pages or all of them may start displaying a 401 error, this happens on collaboration sites and system pages namely Team Sites where you have minimal download strategy feature activated.

Fix SharePoint 401 error


Save publishing site as a template

Save your newly created SharePoint site as a template can save you a lot of time if you want to replicate it again in your environment.

Unfortunately if you used a Publishing Site or if you had to activate the Publishing Features in a Collaboration Site, save site as a template will not be available.

In this article I explain all the steps to bring back this feature to the publishing sites and also the extra steps you may need to activate all site features.

Save Site as Template - SharePoint


Enable Sandbox solutions on SharePoint 2016

Sandbox solutions and web parts are deprecated for a long time but due all the restrictions of the SharePoint app model caused the iframes this is still the best way to deliver rich web parts that fully integrate with the site and other solutions like custom themes.

Microsoft is pushing user’s way from this model by creating limitations to Sandbox solutions like removing sandbox solutions with managed code from Office 365 and deactivating the execution service by default on SharePoint 2016.


Remove Faulty Web Parts from page

If you are a SharePoint developer and the Web Part you are working on is causing so many errors that you can’t even edit the page this tip is for you.

Removing malfunction webparts is very easy all you have to do is access the Maintenance Web Part Page, in this article I’ll show you three different ways to open this page.

Remove SharePoint Web Part


Be prepared to the SharePoint framework

The SharePoint Framework was announced on 4th of May and it introduced a new model to develop SharePoint webparts that is radically different from its predecessors.

Over the years SharePoint development required a specific environment, with SandBox and Farm webparts is required at least one server with SharePoint and Visual Studio to develop and debug, with the App model introduced in 2013 the SharePoint server is no longer needed but it requires Visual Studio and a Developer site collection hosted on Office 365.

With the new framework you are absolutely free to choose your environment, the only requirement is a computer able to run the latest web technologies, you can even use Mac OS or a Linux distro.

SharePoint Framework


SharePoint WSP Repackage

A few years ago I wrote an article explaining how to manually modify a SharePoint WSP solution using a specific software, over the years I got feedback about adware being added to the computers during the installation process of the software.

I recently tried to install this particular software and my antivirus automatically pop up saying that the file was not safe, to get rid of all this issues I decided to build a specific application to repackage all the files inside of the WSP solution.

SharePoint WSP Repackage


Connect external services to SharePoint using Microsoft Flow

Connecting external services to SharePoint specially the ones that are not part of Microsoft ecosystem was incredibly hard but this is about to change with Microsoft Flow.

Microsoft Flow is an event-automation service developed to create automated workflows between your favorite apps and services to get notifications, synchronize files, collect data, and more.

SharePoint 2016 was officially announced last week and it will include a full integration of Microsoft Flow but you don’t need to wait to put your hands in the new version, if you have SharePoint online you can start using it today.

Microsoft Flow


Web developer focused on SharePoint branding, blogger, tech enthusiast. Travelling and sports are my addictions, knowledge and success are my daily motivations.