Microsoft's new look for Document Libraries doesn't seem to use my custom master page. This article (http://www.jasperoosterveld.com/2016/06/adopting-the-modern-sharepoint-online-document-libraries/) says custom master pages aren't supported at the moment. That implies it may come later.

Has anyone else had to address this yet? The primary need of the custom master page is load some external javascript files. Changing the "SharePoint Lists and Libraries experience" from new to classic seems to be the best temporary fix.

1 Answer 1


They've outlined this pretty heavily, what is supported and what isn't here. I know there is a uservoice topic on this that they are considering. As this is something new, expect it to evolve. Their guidance is if you need to utilize a feature listed on that article, use the classic experience.

There are other ways to load external JavaScript without having to customize the master page, look into User Custom Actions. We use PowerShell to staple things like Google Analytics to sites to track views as User Custom Actions, or jQuery.

This however, is still only applicable to the Classic View experience. If you set your tenant to use classic mode, you can use this injection technique to staple your customizations without the needs to modify your master page, which is the preferred method per the PnP group as per last year's Ignite conference.

And the dev group just released a blog post with more information, http://dev.office.com/blogs/update-on-modern-document-libraries-and-extensiblity.

  • The blog post you linked indicated that only URL-based Custom Actions are supported. How are you able to inject custom JavaScript with them? Commented Sep 21, 2016 at 12:17
  • @RobWindsor It implies so, and has to be the case. We see Nintex Forms in the ribbon of our modern lists. Commented Sep 21, 2016 at 12:57
  • Sorry I think we're taking about Custom Actions in two different contexts. I wasn't asking about the ability to get buttons on the command bar, I was asking about the ability to inject JavaScript into the page. You stated in your answer that you were able to get JavaScript into the page using UserCustomActions. I was wondering how you did it. I've tried to add script using Web scoped UserCustomActions and while things work as expected with pages in Classic Mode they don't work with Modern pages. Commented Sep 21, 2016 at 15:28
  • That still isn't possible afaik, the instances where we result to stapling UCAs at the web level are reverted back to the classic experience, I'll update it to be more clear in what I was trying to convey. Commented Sep 21, 2016 at 16:05
  • Trying to do something similar to you @Rob, and afaik there's no way of doing that currently. First answer in the faqs at blogs.office.com/2016/06/07/… states that you'll need to use classic mode to use these 'unsupported features'. Commented Sep 22, 2016 at 23:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.