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
I recently answered a question on SharePoint Exchange, where the original poster was trying to set the default date value of a Date column to “Today’s Date”, but his column was setup as date and time, and he noticed that although the “hour” of the time was set, the “minute” was actually not set. What
I was recently perusing SharePoint Exchange (can’t believe I just used the word ‘perusing’ but I’m running with it) and I came upon an older question that had never been answered. The post reminded me that when working on SharePoint Designer workflows, it’s easy to forget that the actions also have a “Properties” panel with
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
Picture this: You’ve just created your first SharePoint Framework webpart, and you’re ready to slap your company logo on it, and send it out the door. It’s easy – you just reference your image in relation to your webpart file, via a require statement (which will push it into your ‘dist’ folder of assets), and
