Its's more and more complicated to find information about SharePoint. I don't really know why it's so. That's why I often write down the references and examples. Today I tried to remember how to create a SharePoint list with PNPJS and there's a parameter which template you will use.

Below you can find a PowerShell script to copy items from one SharePoint list at one site to another SharePoint list in another site. I use it with several modifications to work with the data in test environments.

When I executed Update-SPSolution command in PowerShell  to update  one of WSP-solutions, I got the error, that 'LOG_BACKUP' is full "Update-SPSolution : Das Transaktionsprotokoll für die 'SP19_Config'-Datenbank ist aufgrund von 'LOG_BACKUP' voll". In English versions of SharePoint the text of the error can be like this "The transaction log for database ‘SP19_Config’ is full due to LOG_BACKUP".

I had a SharePoint online list and I added a new column into it. And then I wanted to work with a data, which is close to be real. So I needed to generate the data and insert it into the list. For the tasks like this I like to use division by module to create semi-random data.

Class to determine if a user is in the SharePoint group or is in the AD Group, which is added to the SharePoint group. So, the admin access to a custom SharePoint module is that everybody, who exists in the admin group, has more data. The admin group is a SharePoint group, which contains SPUsers (from domain) and Domain groups, which contain AD Users. Actual for SharePoint 2016, 2019.

While the development SPFX for SharePoint 2019 once the loading of the webpart at 'workbench.aspx' page stopped. SharePoint server is installed at my virtual machine, the development of SPFX is local. At first I totally could not understand what's wrong. But soon started to look for the reason.

When you make a SharePoint 2019 on-premises solution, you can make not only SPFX solutions, but also old-school WSP-solutions. It allows you not only to use SharePoint API, but also to use your own API services. With SharePoint 2019 you can use WCF service. For example, it’s a good way when you develop an application which uses the external database. This works also for SharePoint 2013 and SharePoint 2016.

If you want to get the Author login from the SharePoint object, for example, list item, you should use 'expand=Author' in the query. It's necessary, but not sufficient. There's one more option, which you must use.

Icons make a better view to any application. And for a developer it’s always a problem to find how to use Icons and especially where to find them. If you work with SharePoint Online solutions, this will help you (and also me) to find a place of icons and how to use them. As far as I often work with FluentUI, the post is about it.

I developed a service for SharePoint 2019 (on premise) and this service should move files from document library to an external storage. The client part is made with SPFX solution – command set. It added buttons to the interface of the document library.