Latest API updates in Client Side Object Model (Dec 2014 CU for SP2013)


We are happy to announce additional APIs being available with the latest cumulative update for SharePoint for client side object model (CSOM). These are updates which are based on the input from the field with multiple different channels. Here’s key updates in the November and December CSOM releases for the on-premises SharePoint 2013.

Controlling detailed versioning settings in list level

  • New public property Microsoft.SharePoint.Client.List.MajorVersionLimit
  • New public property Microsoft.SharePoint.Client.List.MajorWithMinorVersionsLimit

Controlling regional settings in site level

  • New setter for public property Microsoft.SharePoint.Client.RegionalSettings.LocaleId
  • New public method Microsoft.SharePoint.Client.RegionalSettings.Update()
    • You can access regional settings object from Microsoft.SharePoint.Client.Web.RegionalSettings property

Controlling language settings in site level

  • New public method Microsoft.SharePoint.Client.Web.AddSupportedUILanguage()
  • New public method Microsoft.SharePoint.Client.Web.RemoveSupportedUILanguage()

Update on 20th of Dec  – Adding additional language to web has unfortunately a bug and it does not work unless site has already one or more additional languages set, which means that this API does not really usable until this bug is fixed. This will be fixed for future releases and to redistributable version of the CSOM package.  

Controlling auditing settings in site collection level

  • New public property Microsoft.SharePoint.Client.Site.Audit
  • New public property Microsoft.SharePoint.Client.Site.AuditLogTrimmingRetention
  • New public property Microsoft.SharePoint.Client.Site.TrimAuditLog
  • New Class Microsoft.SharePoint.Client.Audit
  • New Enum Microsoft.SharePoint.Client.AuditMaskType
  • New Class Microsoft.SharePoint.Client.AuditPropertyNames

Setting secondary site collection contact in site level

  • New public property Microsoft.SharePoint.Client.Site.SecondaryContact

You can access the December CU updates by using assemblies from updated SharePoint server or by accessing them from Office 365 Developer Patterns and Practices (Dev branch until January master merge). We will also update the redistributable soon in Microsoft download.

 

What about cloud CSOM?

We will update the SharePoint Online Client Components SDK also in upcoming weeks to provide these latest same updates for the Office 365 development. These two packages are unfortunately evolving in slightly different schedules.

 

You need additional APIs in CSOM?

imageIf you have any specific needs for the APIs you need, please let us know using User Voice in below address. We will address these requests and feedback where we can.

Please be patience on the requests, we will address those APIs which we can as fast as possible, but we do not have infinite resources, so we cannot provide any time lines related on the timing for addressing the feedback. Your input will be still highly appreciated and highly valuable for us to align the resources on the most needed capabilities.

 

Office 365 Developer Patterns and Practices

Office365PnPLogoRed_thumb1We will provide updated samples and scenarios based on these APIs in the Office 365 Developer Patterns and Practices guidance, which contains already more than 100 samples and solutions demonstrating different patterns and practices related on the app model development together with additional documentation related on the app model techniques.

Check the latest updates directly from the GitHub project at https://aka.ms/OfficeDevPnP. Please join us on sharing patterns and practices for the community for the benefit of the community.

“From the community for the community” – “Sharing is caring”

Comments (16)

  1. Andrew Connell says:

    Hey great to see these improvements! Now… how the REST API getting some love and FINALLY (2+yrs later) getting support for taxonomies & workflow services.

  2. Koen Zomers says:

    Lovely to see this nice overview of added CSOM functionality! Thanks for sharing.

  3. Bruno says:

    Great news! What about JSON Light support on REST API for SharePoint on-premise?

  4. Vesa Juvonen says:

    We should see improvements in the REST area soon as well, but nothing to report right now.

  5. Ashish Trivedi (Readify) says:

    CSOM updates are going great. Really loving the way CSOM is getting more APIs.

  6. Yavnish says:

    Great, but has anybody any idea that when new assembly "Microsoft.SharePoint.Client.Site.Audit" will be available?

  7. Vesa Juvonen says:

    Hi Yavnish,

    that API is already available in on-premises (starting from Dec CU). It will be available for Office 365 around end of February. No locked date yet.

  8. Yavnish says:

    Thanks Vesa Juvonen, thanks for this valuable information.

  9. Mallikarjun says:

    Hey Vesa, thanks for the awesome post.

    Can we know the date till which these APIs will be available for SharePoint Online??

  10. Vesa Juvonen says:

    Hi Mallikarjun,

    no news on locked date. We will communicate changes immediately when those are available.

  11. Vivek says:

    Hi Vesu, I am not able to find Client.Audit. I have downloaded the latest CSOM from this link: http://www.microsoft.com/…/details.aspx.  Could you please share equivalent REST API?

  12. Vesa Juvonen says:

    Hi Vivek,

    like mentioned in previous comments. These APIs are currently only available for on-premises starting from December CU. We do not have a date yet for cloud CSOM update. We will update the situation when redistributable package has been updated.

  13. Loic says:

    Hello Vesa, do you have more info about the availability for Office365 ? really looking forward for this upgrade !

  14. Vesa Juvonen says:

    Loic,

    unfortunately nothing new to report at this time. Will post a blog post immediately when there's new package available with details on the package.

  15. Wesley Fine says:

    I need this!!  Thanks Vesa and keep this crowd up to date.

  16. Syed says:

    Any news yet on REST API update for secondary contact?

Skip to main content