In this article, I will cover some different ways you can use to easily enable SharePoint spaces in a modern SharePoint site.
This blog post covers an easy way to add the request body of a SharePoint event receiver into an Azure storage queue using a Azure Logic App
In this article, I will show you how to create an Azure Function to merge PDF files stored in SharePoint. The Function will be a generic service, which receives a list of file paths to merge.
This blog post contains a simple PowerShell script that you can use to find all SharePoint files from a certain file extension in a site and export to CSV
This blog post contains a simple PowerShell script that you can use to find all SharePoint files from a certain file type in your tenant and export to CSV
You can find many problems when using Power Automate and Azure Logic Apps with complex SharePoint lists. This article will cover another one that cause triggers to break. If you use the "When a file is created or modified in SharePoint" trigger, keep reading.
In classic SharePoint sites, it was possible to redirect users to a different site using a few different approaches. But modern SharePoint sites are more restrictive (for good) and offer different features that require different approaches. Fortunately, if you need to redirect users when they try to access the homepage of a specific site, this can be easily achieved using a simple no-code solution.
If you use modern SharePoint libraries with large collections of folders, you will likely feel that navigating your way around the folders is no easy task. So I built a "super simple" SharePoint Framework list view command set extension to address this problem
Some time ago, modern SharePoint sites received a new feature: modern Document Sets. In order to enable and use of this feature, "all" you have to do is enable the "Document Sets" feature under Site Collection Features and add the relevant content type to a library. Simple right? Well...perhaps not so simple if you try to do this programmatically.
A SharePoint library (root folder) or library folder fields can be configured to use default values. For example, if you configure default values in a folder, documents added to that folder will inherit those field values by default. This functionality is great when you have a project that heavily relies on metadata being inherited through multiple levels of information.