The other day I was working on an SPFx solution that needed to verify if a folder existed, or else create it. Think of it as EnsureFolder, a throwback to one of my favorite SharePoint methods, EnsureUser. Upon not seeing anything in a quick scan of Intellisense, I went to the PNP JS Documentation to
I had a great time speaking at SPS New England with Chris Kent this past weekend. Our topic was “Getting the Most Out of SharePoint Patterns and Practices (PnP)” and with Stranger Things 2 just being released, as well as Halloween right around the corner, we chose to brand the entire presentation with a “Stranger
While this was originally planned as a 3-part series, something recently happened that has caused us to need to make some changes to our code. The cause of this effect is the release of the SharePoint Framework 1.2.0 version, which includes Release Candidate code for SharePoint extensions. Series Recap: Part 1 – Create the Content
I was recently upgrading my local version of the SharePoint Framework, so that I could get the latest Release Candidate (RC) for the SharePoint Framework extensions. While doing this, I decided to go ahead and get the latest version of all of the related modules, by issuing the following: Running the above updated my version
In Part 1 of our series we created a declarative list to hold the placeholder content for our site. In Part 2 we utilized an Application Customizer extension to grab that content and place it into the available placeholders. In this third part, we’ll modify our data model to cache those results in localStorage, to
Series Recap: Part 1 – Create the Content Repository for managing your Placeholder content Part 2 – Inject your managed Placeholder content into your pages Part 3 – Cache placeholder content in localStorage Part 4 (New!) – Update code for the 1.2.0 SharePoint Framework Extensions Release Candidate Welcome back! Although this is only the second
Have you seen the new SharePoint Framework Developer Extensions preview? If not, check it out here! One of the many exciting features included is the ability to inject content into placeholders on all pages. This is a great way to be able to customize the look and feel of your site, but without having the
Chris Kent very quickly discovered an issue with the default schema the new SharePoint Framework Extensions Developer preview includes, and noted that bug here (thanks, Chris). The summary of the issue is that f you’re working with the new developer preview, you’ll currently get a schema error on the {AppName}ApplicationCustomizer.manifest.json file located within your {AppDirectory}/src/extension
