I have a client that has over 50 subsites of the root site in a SharePoint site collection that are all pretty much the same. There’s a site for each county in the client’s state, each one with web parts to show some data from the root site that’s relevant to that specific county (contacts’ information, documents, that kind of thing). Whenever they wanted to make a change to, say, the contacts web part for these county site, they had to modify over fifty copies of the same web part. Tedious to say the least. After a few rounds of making these kind of repetitious modifications it was decided that I would need to come up with a solution to make managing this stuff much easier.
So I did.
Don’t worry, it’s the good kind of Script Injection!
While reviewing some requirements for a project, I noticed that they wanted an inherited Top Navigation and Master Page to be part of their site creation process in SharePoint 2013 On-Premises. One of the client’s requests was that we not use server side code (C#\VB). Since I’d never done this in REST API, I decided to do a bit of research into it and came to the following conclusions…