Introduction SharePoint 2013 has greatly expanded the REST services available to developers. With this, we have much more SharePoint functionality exposed via JSOM and Web Services . The goal of this article is to provide how to perform basic create, read, update, and delete (CRUD) operations on lists and list items with the REST services. SharePoint REST endpoint Overview: The following table contains typical REST endpoint URL examples to get you started working with SharePoint data. Prepend http://server/site/_api/ to the URL fragments shown in the table to construct a fully qualified REST URL. Below is a list of the basic commands used to get List Items from a SharePoint List through the SharePoint 2013 REST Services. URL endpoint Description Supported HTTP Method /_api/Web/Lists/ getbytitle('listname') Getting a list details by its title and updating it as well. Ifanyone changes your list title, your code will break. ...
Introduction When versioning is turned on for a SharePoint list or document library, there are times when you may need to report on the number of list item versions, or delete versions that exceed a threshold. These scenarios can happen if; 1. Version limits (for the maximum number of major/minor versions) were not set, and the list has too many versions 2. Version limits are being applied or reduced, and you need to retrospectively delete all the versions in a list that exceed the new threshold* 3. You are performing an upgrade, and you want to prune the versions of pages in the pages library (on a publishing site) 4. You want to run a report to determine how many items in a list have more than "x" number of versions *When the version settings are changed on a list, existing versions on existing items in the list are not changed until the item is modified. Therefore, if you reduce the maximum number of versions to be kept for items in a list, the changes only take effec...
DECEMBER 19, 2017 ~ NICOLE PRESTBY I had a requirement from a client recently to show all list item attachments on the various task forms in an approval process – which, if you think about it, makes total sense. With any project, we always have a common goal of making the user experience as seamless as possible for our users and approvers. So, why wouldn’t we provide all pertinent information needed (including related documents) to complete the requested review and approval, right there on the task form? I found a post on Nintex Connect which walks through meeting this requirement by leveraging a custom action created by Nintex Technical Evangelist, Vadim Tabakman . But, what if you don’t have access to deploy a custom action to your SharePoint environment? In this case, I actually didn’t have access to the client’s server. So, I decided to come up with a solution that would produce a similar outcome, without the...
Comments
Post a Comment