Posts

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!

Acknowledging Microsoft’s warning, I vowed to stay in the box and not rely on any classes that were not included as part of my solution. Other than “fixing” the workbench to behave like an actual page in SharePoint, I went a long time before breaking my vow. I have a client that complained non-stop about the white-space between web parts on their intranet homepage. I calmly explained multiple times why Microsoft chose to design the modern page with this white-space, but they insisted that I needed to change it. Eventually, the “client is right” mantra won, so I built a web part that would allow the client to adjust the horizontal and vertical spacing between web parts. Again, I warned them that one day the page might just disappear. Happy client == happy paycheck!

As soon as I got the call about the white-space being back, I had a pretty good idea what happened. Sure enough, when I cracked open the Dev Tools of my favorite browser (Edge), it didn’t take long to find the issue. The two classes I used to adjust spacing were no longer there. There were new classes in their place that seem pretty cryptic, having what appears to be an identifier (partial GUID) as part of the class name. Those class names did not look like a stable place to be targeting at all. To Microsoft’s credit, they (mostly) took the old class names and moved them into an attribute called data-automation-id. Not only did this help track down what had changed, but gave me new targets to “fix” my broken web part for now.

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. They also block access to all non-company tenants. Fortunately, I am able to do my development “off network” and once everything is ready, I move the code inside the firewall. Since this was an update to an existing web part, I knew deploying it to the same tenant as the existing web part was going to be tricky. The existing web part is on the company intranet home page, so getting into a site for testing without affecting the original web part meant deploying into a “QA” site app catalog. I thought this would work and there shouldn’t be any conflict. Famous last words …

There were definitely doubters, but the North American Collaboration Summit has successfully executed the first “hybrid model” conference. And the results were better than any of us imagined.

• To read a full summary, including lessons learned, from conference organizer Mark Rackley, click here

The decision to go

Honestly, my beautiful wife, Tracy, and I were excited to just get out of the house and go somewhere. We have tried hard to abide by the recommended protocols of social distancing and protective measures. For months, we have limited contact to just our family and a very small number of selected friends. I was nervous about attending such a public event, but after talking to Mark about the measures that were going to be taken by the hotel where the conference was being held, the “contract” that all attendee and speakers would abide by and the current COVID-19 situation in the Branson, MO, area, we decided the risk was within reason to attend the event in person.

UPDATE-MARCH 30

Due to the global pandemic, NACS has been rescheduled for Sep 28-30, 2020. Click the image above for the latest information