Office Development MVP / Office 365 & Azure Development

Some time ago I wrote about things to check in your SharePoint Framework application customizer for making sure it behaves correctly on navigation events. This included checks to see if you navigated to another page, different hub site and site with another language. In most cases, these are the checks that you want to put in place, to make sure that your application customizer renders the right data after a navigation event.

One of the things hardest things when creating and maintaining a product is localization. It requires a lot of testing, validation and follow-up. In SharePoint Framework projects it is no different, maybe even a bit harder, as the localization files are created per component. This means that you might have to take care of duplicate localization keys and labels.

After almost three years, I finally made my over to a static site generated by Hugo. From the moment I started blogging in 2010, I used Wordpress. Wordpress was the best option back then. As the hosting company which I used only supported PHP, and I also got into coding by learning PHP when I was a student.

It appears that some time ago (weeks/months), the unique ID of a SharePoint homepage is not unique anymore and is shared with other homepages pages in your environment. The problem occurs when creating new SharePoint sites. Once the site has been created, it will most likely share the same ID with a couple of other homepages.

When setting up a portal on SharePoint Online these days, you most likely will do it with a hub site driven approach. With hub sites, you have one root site collection, which can be seen as the parent, and all children are associated with it. Hub site association When building solutions for your hub sites, you probably need to know on which hub site your solution is currently running.

Version 1.14.0 of the SharePoint Framework React Controls (@pnp/spfx-controls-react) has been released. This is an open source library that shares a set of reusable React controls, which can be used in your SharePoint Framework solutions. This release includes the following changes: Enhancements German translations added for attachment and RichText controls #333 SecurityTrimmedControl: Added a wrapper className property for the parent element #325 ListPicker: Add ability to filter the control via OData #319 IFrameDialog: closing dialog on commit #313 WebPartTitle add support for section background color #258 Fixes