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?
Having different Views in your SharePoint lists & libraries can be very useful. It allows you to see information in a different way pretty quickly, and remove the noise. In this post, we’ll have a look at the available options so you can choose what’s best for you! Default View Out of the box, SharePoint sets the default view to “All items” for lists, and “All Documents” for libraries. Meaning there’s no specific filtering.
First post of 2021, and in this brief post, we’re going to see how we can check if our SharePoint Online sites have a Microsoft Teams team associated to it. Why is it brief? Because PowerShell PnP is making it very easy! 🤩
From now on, we’re also going to focus on the new PnP PowerShell module available for PowerShell Core. This is the module we’re familiar with, but available on Windows, MacOS, or Linux!
I have created a new video on my Youtube channel to help you getting started with PnP PowerShell on PowerShell Core.
If you’re used to take advantage of the amazing SharePoint PnP module, this is very important because things are going to change in a couple of months! As PowerShell Core is the future (use PowerShell on Windows, MacOS, and Linux), you need to be prepared. Therefore, in this video, we’ll start from scratch: