I used EventCalendar component with resources and timeline view, the default interval is 1 month, I also add week numbers to the header. I wanted to fit the calendar to the page without horizontal scroll.

The queries to get all the list items, get list items with specific field values, get list items by ContentType Name. The most of the time I spend with the last one.

Many times I told myself not to work with SharePoint, but it's forever with me 🙂
My colleague asked to help him with a problem with modern lists. There some simple fields, without lookups. But there's an error in displaying items. I spent about an hour to determine the problem - created a copy of the list, removed all items, added items with only 1 filled field. It worked in classic view, but not in modern.

Once I tried to make the application to migrate a custom data source from SharePoint 2010 to SharePoint 2019 on-premise. To make it easier, I decided to make to separate solutions – the first one to export the data from SharePoint 2010 from the list to JSON and attachments to local folder(CSOM for SharePoint 2010 sucks) and the utility to import data to SharePoint 2019 via REST.

The method to expand all the events in Calendar View on load using Content Editor WebPart. You should add this code. You should copy and paste it to html file, save this file to document library and set its path into the settings of CEWP.

To retrieve a SharePoint version there's no need to go to Central Administration. You can easily see it if you enter the URL

http://mig1/_vti_pvt/service.cnf

(read more...)

With SharePoint 2010 you can disable usage of modal windows in List settings. But if you use calendar view, it does not matter what you have installed in the settings – all the list forms will be opened in modal windows. How to disable them?

This post is about SharePoint web services. In SharePoint 2010 you can use only SOAP requests to get or to send data from or to SharePoint web sites. A bit below in this post you can see the list of WSDL URL addresses.

(read more...)

After installation several Windows updates on servers with SharePoint I had started to recieve the warnings "The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.". It means that I can not use PowerShell for administration SharePoint.

(read more...)

Today in a test SharePoint environment I found that I don't have one of SharePoint features which I have in the productive environment. I reinstalled the solution with this feature several times, but it hadn't appeared.