Installing SharePoint patches have been an issue since forever. Over the years, the strategy from Microsoft has changed a couple of times. CU became PU’s, language packs were removed. Worst thing was when Microsoft decided to roll out patches via WSUS / Windows Update…
Then SharePoint 2016 came and Zero Downtime Patching was introduced. Reason is that Microsoft now has to patch O365 as well, and there should not be any downtime.
My initial thought was this would be amazing, but I’m slightly disappointed. Yes, you can install patches without any downtime, but it is still a very cumbersome and manual process. This video explains this very well in details. I really appreciate all the documentation and blog posts from Microsoft, but I don’t understand why in 2017 we still have to execute so many manual steps to install SharePoint patches.
Then I found SPPatchtify which solves this! Continue reading
When I heard about Microsoft Teams, I was very excited from the start. I’m using Slack a lot for GitHub projects and for some internal projects, as there is no alternative in Microsoft. Teams is positioned as a Slack competitor, and when it was available as public beta, I immediately contacted our Office 365 admin to enable it. I’ve been using it for a couple of weeks now, and I want to share my experience with you!
Announced at the “Future of SharePoint” event, was the SharePoint Framework. And it is in public beta since this week! I was one of the lucky persons who had access to the internal repository, so I already had a play with it before. Unfortunately I could not blog about it, as it was under NDA. I will talk about how it will fit into the existing SharePoint development infrastructure, and start with some history 🙂
After my blog post yesterday about Flow, I got a request from a user to build a Flow for Salesforce that does something when an Opportunity is closed, and checks if it was won or lost.
I love feedback, so I decided to build that flow. The result? Check out below email:
If you’ve followed my blog, you know I’ve been looking at PowerApps. PowerApps consists of two parts: Flows (formerly Logic Flow App) and just Apps. Flows allowed you to do things like “If someone tweets about my company, send me an email”, or “When a record is added to SalesForce, add an item to a SharePoint List”. Microsoft has now taken out Flows / Logic Flow Apps, and released it as a separate product: Flow. I think this is a good step, PowerApps can then focus on enabling power users to create mobile apps. I will briefly discuss what Flow is, and show an example of an automated tweet translator emailer. Continue reading
One of the most important features of SharePoint is the document library. SharePoint is a document management system since 2001, so the document library is one of the key features. Initially the only instance of the document library was within team sites. In later versions and in Office 365 there are other locations to store documents, like OneDrive for Business.
The user interface of the document library hasn’t changed much since SharePoint 2007. Yes, in SharePoint 2013 drag-and-drop was introduced, the UI has been polished, but in basis the UI was the same. And the confusing part is (was?) that the document libraries in SharePoint looked different than e.g. Onedrive for Business. That has now changed! Continue reading