Wouldn’t it be great if we could just open our browser, log in to our SharePoint site, and use the browser to do our testing?
Wouldn’t it be great if we could just open our browser, log in to our SharePoint site, and use the browser to do our testing?
There are times when you might want to test your application against real data in SharePoint, instead of mock data. Wouldn’t is be great if we could have a proxy to send these requests to, and it will take care of all the authentication stuff for us.
SharePoint exposes a REST interface that allows us to perform basic create, read, update, and delete (CRUD) operations on its entities. These operations are performed by constructing a RESTful HTTP request, using the OData standard, that corresponds to the client object model API you want to use. Each SharePoint entity is exposed at an endpoint Read
SharePoint PnP reduces the amount of code you write. PnP is essentially, a trimmed version of the Client Side Object Model (CSOM) and the JavaScript Object Model (JSOM) libraries.
Get to know ShaprePoint Field Definition Schema and how to use it with PnP Powershell
Filtering on columns are very easy but not so much for lookup columns to another list for some of you. In this post, I will show you how you can easily do it.
The SharPoint person or group field exposes a handful of important properties. This post will list them and serve as a reference to anyone who needs it.
The usual way to call the SharePoint REST API was to include in the header request: accept: application/json; odata=verbose. The good news is that, this header is now optional, and more OData options have been added.