SharePoint Site Scripts and Site Designs - April 2018 release
We are happy to announce the availability of additional Site Script Actions for SharePoint Online Site Designs and Site Scripts. These new actions will enable you to further configure automatically thenewly created site collections for your employees and will reduce the requirements of having external services integrated with the provisioning process.New updates to Adobe Document Cloud show the power of integration with SharePoint and OneDrive
Well-integrated tools save you time by avoiding distracting context switches and providing tools right where you need them. Applications like SharePoint feature many ways to extend many user experiences. See how a Microsoft Partner - Adobe - is leveraging these integration experiences to improve productivity across products.Take advantage of the SharePoint Look Book sample designs in your own environment!
SharePoint Provisioning Service can be used to provision sample content (like SharePoint Look Book site samples) and example solutions to any tenant in the world. This service is brought to you by the SharePoint engineering together with the community and it's currently in public preview status as we polish the experience based on your feedback.
Announcing Availability of Feature Pack 2 for SharePoint Server 2016
When we launched SharePoint Server 2016, we shared the vision for SharePoint Server 2016 as a foundational release, born in the cloud, and built for continuous innovation. Today we’re pleased to announce our continued investments on this journey and commitment, the availability of Feature Pack 2.
Update file metadata with Rest API using ValidateUpdateListItem in SharePoint on-premises
This post is a contribution from Aaron Mio, an engineer with the SharePoint Developer Support team. Lately. I came across an issue of using REST API ValidateUpdateListItem() to update listitem metadata. There’re a few blogs published on method ValidateUpdateListItem() for SharePoint Online. A few benefits of using ValidateUpdateListItem are: Update list items without increasing its item version (see this blog for details). Easier to update some types of metadata, like Taxonomy, People and Lookup fields (mentioned in Robert's blog). Besides Robert's blog, Andrew’s blog also presented detailed info about how to set various types of fields with ValidateUpdateListItem(). My issue was to update Editor and Author fields for a listitem on SharePoint on-premises (SP2016 and SP 2019) without increasing item version. Both Editor and Author are People and Group (Person) field. According above blogs, you can set the Person field, like: "[{'Key':'i:0#.f|membership|aaron@contoso.onmicrosoft.com'}]" This works fine with SharePoint Online users. However, it does not work with SharePoint on-premises users, although no error returned from the method. After some testing, I found that for SharePoint on-premises users, you need to set the Persons field like below: "[{'Key':'i:0#.w|aaron@testdomain.com'}]" The sample below updates the Editor and Author fields on SharePoint on-premises (SP2016 and SP2019) without increasing item version. { "formValues": [ { "__metadata": { "type": "SP.ListItemFormUpdateValue" }, "FieldName": "Editor", "FieldValue": "[{'Key':'i:0#.w|aaron@testdomain.com'}]" }, { "__metadata": { "type": "SP.ListItemFormUpdateValue" }, "FieldName": "Author", "FieldValue": "[{'Key':'i:0#.w|aaron@testdomain.com'}]" } ], "bNewDocumentUpdate": true } The REST API ValidateUpdateListItem() on the ListItem object is much easier in providing the Person field values to update. In addition, it has an option bNewDocumentUpdate to specify how you want item version to be updated.
