Conferences are slowing coming back and I am personally looking forward to talking to attendees, sponsors, and speakers in person again. First on the agenda this year is the M365 Collaboration Conference (formally the SharePoint Conference) in Orlando, FL, Jun 8-10. The “big” conference is still scheduled for Las Vegas in December, but this is a hybrid event that promises to be an exciting time as we transition from the virtual world we have lived in for the past year.
One of the most exciting changes to SharePoint in the last few years is the advances in custom formatting of columns, views, and forms. These capabilities have transformed lists from functional tools that are pretty boring to exciting, dynamic, visual presentations of data with colors, icons, and almost anything you can design in HTML/CSS. By default, most of the custom formatting samples for columns are shown in a single view, but it is just few steps to make this formatting active in every view.
As 2020 ends (finally!), I realized that I neglected to post about an acheivement that I am very proud of. Last month, I was confirmed as a Microsoft Certified Trainer (MCT) for 2021. This is my 5th MCT certification and I even received a nice polo shirt for the 5-year acheivement. I am very proud to be counted among professional instructors in Microsoft technologies and look forward to more opportunities to use my certification help educate others.
Recently, I built a web part for a client, which led to a discussion about why the web part background was static white, which did not reflect the branding on the page. My quick fix was to just change the color manually, but now I wanted to know more about how I could build webparts that are aware of the area that they are in. It turns out, there are several options, depending on the capabilities needed and the web part framework.
Microsoft warned us! The Document Object Model (DOM) on web pages was a common target in my pre-SPFx solutions, especially the ones that used jQuery. When SPFx came along, Microsoft was very clear that the classes and element ids on the modern page were not an API. By that, they meant that there was no contract with developers that those values would not change in the future. The future is here!
I recently ran into a situation where building and debugging a SPFx web part seemed to go off the rails. Then I figured out that my normal pattern of skipping the ‘gulp clean’ command during project deployment had cause what I thought was bizarre behavior in Site Collection Features and toolbox. I was working for a client that does not have a dedicated development or QA environment due primarily to political reasons.
Have you ever found yourself looking for an icon, but not able to quite track down the perfect one? Between SPFx projects and the new modern list formatting capabilities in Microsoft 365, I am often looking for the icon to perfectly represent my idea. Until now, this process involved browsing through the Fluent UI website in hopes that I will stumble across one that works. Now there is a better way: Flicon.
For the several years now, I have concentrated on helping developers to get started coding in the SharePoint Framework (SPFx). My primary message has always been that, “despite it being a complete departure from previous coding approaches in the SharePoint, it’s not as difficult as it seems and you should just give it a try.” I am updating that presentation to include recent changes to SPFx as I prepare for upcoming engagements at North American Collaboration Summit (NACS) and ShareCloud Summit and will post it on this site when available.