In case you haven’t seen, there’s a new feature when you share a document from SharePoint Online: Open in review mode only. In this blog post, we’re going to have a look at how it works, and what’s the experience from a reviewer perspective. How does it work? When you’re about to share a document, you’ll see the option in the popup. You must have allow editing checked, or the option will be greyed out.

There are so many features in SharePoint (on-prem & online) that some may be overlooked. Lately, I was working on a PowerApps with Power Automate in the background, and I needed to set default values for some items’ fields, and surprisingly, my first thought was to set those values within the flow. But I have noticed a couple of things by doing it this way. First, that Power Automate was slow to set the value, and second, it was also adding a new version (i.

Did you know that there’s also a PnP PowerShell command that will use a REST request? Meaning we’ve got a different syntax, (sometimes) better performance, but the same results. In this post, we’ll create items in a SharePoint Online list using the Invoke-PnPSPRestMethod by importing a CSV file. Let’s go! 🚀 REST API If you’re not familiar with SharePoint REST API, have a look at the official documentation. CSV file Nothing specific in the .

In this post, we’ll have a look at a specific cmdlet: Set-PnPListItem. We have a couple of interesting parameters (including the -Batch one!), depending on what we’re trying to do. If you used this cmdlet before, and particularly to update something without creating a new version of the file, we used the -SystemUpdate parameter which I’ve found great and really useful. Now we have new ones which are under -UpdateType:

Recently, I’ve seen a few requests about how can we get who deleted files in a SharePoint Online site? You know… that “Deleted by” column in the recycle bin? But have you tried to get the value of that column with PnP PowerShell? Of course you have, by using the DeletedBy property of Get-PnPRecycleBinItem… And have you noticed something like, blank results? 😟 Well, I’ve stumbled on that too! Some CSOM objects are not returned (blank) and this is not an easy fix unfortunately, BUT changes might come in the future.

SharePoint Online has come a long way visually from the old days, and also from an “out-of-the-box” functionality point of view. A lot of things don’t require organisations to code or script to get something decent. BUT, we also have fantastic contributions from the Community with List Formatting samples! And that’s what we’re going to look at today! So… Do you want your SharePoint lists and libraries to look better? Yes?

In today’s post, we’ll have a look at something that could potentially be your mini “re-organisation / migration” project. We’ll see how to copy or move files to another location, either on the same site but different library, or a completely different site. Starting Point Let’s have a look first at our current (dummy) structure. We have SitePnP1 where we’ll use the default Documents document library. Inside this library, we have a folder called Folder1 with files inside (nested files).

Did you know that fields in SharePoint Online set as “required” are not so… required anymore? It may be a pain for some, but they are now used as ‘guidance’ with a yellow background color instead and other signs like the red dot in the View. It means that users can upload documents without filling the required values and leave the site! 😕 This is not ideal if you use this metadata for your Search is it?