To update the Created Field for SharePoint list item you can start the script like this. The most important here is the 'fullcontrol' permissions and '-UpdateType UpdateOverwriteVersion' parameter in the request.

For a process I had to update the Author field in SharePoint online list item. This time I decided to use PnP.Core instead of PnP.Framework. Was it worth it? I don't really know, but the method is not the most difficult part of the task.

Here I will write down the steps for creating projects for SPFX solutions. The prerequisites - Node, Yo and spfx-fast-serve are already installed.

I used Material UI DataGrid (@mui/x-data-grid": "^7.12.1") in SharePoint spfx webpart solution. Obviously, that wasn’t a good decision, but too much was already done.

In this post you I will write how to get available options from the SharePoint field 'Choice'. I often use it, and sometimes I need to use it in customizations or reports.

There's a small snippet to check if current user permissions are enough to save list items. It can be used in SPFX webparts with PNP JS.

When you work with common modern React application (React > 16) and webpack, it's easy to create .env files and use them in the project. But if you work SPFX solution, which uses GULP, it's a big mess. That's why I decided to describe the sequence of steps how to use different environments in SPFX solutions.

There are a lot of cases when you need to get the items by the author. For me the only correct way to get the SharePoint list items by user with CAML is like this:

<Where><Eq><FieldRef Name='Author' LookupId='TRUE' /><Value Type='Integer'>123</Value></Eq></Where>

You can delete timer job only with PowerShell. Why? I guess you know why 🙂 The most popular reason is the duplicating of timer jobs. To delete a timer job, you need to know the ID. And you can get it also with PowerShell or with GUI.

In a recent project, I needed to create a SharePoint list and add an index to it, triggered by the addition of a web part to a page. The goal was to fully automate the process using the SharePoint REST API, eliminating the need for any manual intervention by administrators. Here's how I achieved this.