SharePoint
Feedback by UserVoice

SharePoint Dev Platform

← SharePoint Experiences in Office365 and/or SharePoint Server

Welcome! This is your place to suggest ideas or vote for ideas for improving the SharePoint Dev Platform.

How to submit a new idea

  1. Check if it's already been suggested. If it has, vote for it.
  2. If it's new, submit it in 50 words or less.
  3. Gather support!
  4. If your idea receives over 100 votes in 90 days, we will respond.
    If not, we will close it.

Want to engage further? Please visit the SharePoint Community

Note: we have partnered with UserVoice, a third-party service and your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy, including the license terms. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.

I suggest you ....

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

  1. Add managed metadata term store operations to REST API

    Currently term store operations are only available via JSOM. It would be nice to see this added to the REST API as well.

    1,510 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    31 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →
    working on it  ·  SharePoint Dev Platform Team responded

    Thanks for your feedback! Just a note to let you know that we’re building your suggestion now. We do apologize for the delay on getting this moving, but we are now working on exposing term store operation properly with REST API/Microsoft Graph. We will be covering any updates on the API status, before the actual release, in the SharePoint Dev community calls. Thanks, everyone for your input around this capability.

  2. Support .NET Core with CSOM

    Support .NET Core with CSOM

    1,093 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    40 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →
    working on it  ·  SharePoint Dev Platform Team responded

    Thanks for your feedback! Just a note to let you know that we’re building your suggestion now. Just to be precise, we are looking into having a .NET Standard version of the CSOM package, so that it’s usable in both older .NET versions and also in the .NET Core. No ETA at this point, but happy to inform that work is in progress.

  3. Provide CSOM and REST API for recurring calendar events

    There is no obvious way to get details about a recurring calendar events through the CSOM or REST API.

    When querying a calendar list only one item is returned for the calendar recurrence item. Only one field identifies this is a recurring item. the fOccurrence field is a boolean field.

    When using the server side object model, properties are available to expand recurring calendar events to get the individual recurring items.

    The only way to do this for client applications is to go back to using list.asmx which is not great and I'm not sure how long this will be…

    536 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    16 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →

  4. Ability to use App-Only calls to create modern sites

    Provide support to create modern sites using App-Only calls.

    342 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    16 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →

  5. List.NavigateForFormsPages support in CSOM

    Currently it's not possible to set the List.NavigateForFormsPages property through CSOM as it is in the server API.

    314 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →

  6. Allow publishing of content type hub content types via CSOM

    You cannot currently use CSOM to publish content types in a content type hub in O365. Right now you must imitate the page post back to do it.

    283 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    8 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →

  7. REST API citizenship! (surface, roadmap and change log)

    Besides the lack of detailed documentation around the REST API, given its importance as a major entry point for apps, it needs to be treated with more respect as a service offering. It's currently being updated in CUs and on SharePoint online without any notification of the changes being made (such as the $metadata endpoint appearing - was it in the August 2013 CU for on-prem?). We either need it to be released in a non-breaking change model (URL versioning such as the Twilio model), or messaging needs to be improved so we know when things are going to be…

    246 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →
    working on it  ·  SharePoint Dev Platform Team responded

    Thank you for your input. REST APIs are absolutely critical for the SharePoint Framework and for other customizations. We are working on improving the existing documentation and to ensure that you can more efficiently take advantage of the SharePoint REST APIs in your development.

  8. SharePoint 2016 On Premise _api/Web/Lists('listID')/subscriptions support (WebHooks)

    Please provide subscriptions API (_api/Web/Lists('listID')/subscriptions support (WebHooks)) SharePoint 2016 On-Premise which helps in webhooks, desktop notifications, mobile/push notifications and cross platform notifications to name a few.

    224 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →

  9. Provide the ability to write to Managed Metadata via app-only policy

    App-only policy in the SharePoint App Model is very restricted regarding Taxonomy operations. Even if an app is granted full control over the tenant, it lacks the permission to do anything but read operations on Taxonomy. Please provide the ability to create Groups, Term Sets and terms using app-only policy.

    194 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →

  10. Provide flag to enable\disable event firing from Remote Event Receivers

    Provide option to enable\disable event firing from Remote Event Receivers in SharePoint Online (CSOM/API) similar to SSOM - EventFiringEnabled

    175 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →

  11. Add information management policy management to CSOM

    Add support for managing information management policies, and especially retention policies, on content types and in libraries using CSOM. These are the objects largely in the Microsoft.Office.RecordsManagement.InformationPolicy assembly, such as the Policy, PolicyItem objects, etc.

    166 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    4 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →

  12. API for "Create Team from Template" with Site Design

    We can do templating on SharePoint, through Site Designs and Site Scripts. We now also have the option to "Create a Microsoft Teams from Template".
    Unfortunately, both do not work together. We either have a templated SharePoint site with a generic Teams or a templated Teams with generic SharePoint site.

    I would love the possibility to combine both templating options. Preferrably with an API from day 1.
    This would give us an end to end templating scenario, where we can create preconfigured Teams with a preconfigured SharePoint site. (In the future, hopefully with a preconfigured Planner etc as well ;)…

    162 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →

  13. Import XsltListViewWebPart definition

    It is actually possible to import the definition of a XsltListViewWebPart via LimitedWebPartManager in CSOM. However, not all properties are supported. Important properties like XmlDefinition, Toolbar, ViewStyle, .. are being ignored. There's no possibility to have everything set correctly not even manipulating the backed view after importing the WebPart. Please read also this discussion:
    http://sharepoint.stackexchange.com/questions/90433/add-document-library-xsltlistviewwebpart-using-csom-or-web-services

    158 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →

  14. Line up list item pagination with REST API using $top and $skip

    Actually, the only way to paginate list items using the new REST APIs is to use __next property. There's no way to have a full working pagination using $top and $skip token as for any other REST call.
    See my comment here:
    http://msdn.microsoft.com/library/d4b5c277-ed50-420c-8a9b-860342284b72.aspx

    157 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →

  15. Please add the ability to set column default like you can in Object Model with documentmanagement.dll

    Need to do this in CSOM
    $columnDefaults = New-Object Microsoft.Office.DocumentManagement.MetadataDefaults($list)
    $columnDefaults.SetFieldDefault($Folder.Folder, "TestMMSColumn", "1033;#" + $term.Name + "|" + $term.Id)

    152 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →

  16. Provide the ability to identify features that are deactivated using CSOM

    It's currently possible to identify the features that are activated at the Site and Web level using CSOM, it isn't however possible to determine which features are present but not activated using CSOM. It would be great if this feature could be added!

    149 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →

  17. Add CSOM support for connected WebParts

    At the moment it does not seem possible to create WebPart connections via the Client Side Object Model.

    130 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    5 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →

  18. Improved API feedback around throttling

    Currently working with the API's for drive, graph, sharepoint are very difficult due to the throttling that can be encountered.

    Each api offers different guidance to avoid throttling. Example are:
    1) use a special user-agent header
    2) respect the retry-after header

    Speaking with microsoft representatives they instruct us to perform major api processing in off peak hours. Additionally tenant's can have hard locks placed on them.

    This request is to get better information around tenant usage returned in the API's.

    1) If a tenant is hard locked, tell us in a distinct message so that don't just hammer the requests…

    128 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →

  19. API support for followed sites

    There's an undocumented API (https://tenant.sharepoint.com/_vti_bin/homeapi.ashx/ ) to follow sites and query data around those concepts. For corporate intranet scenarios, we often want to present the data a different way, surfacing native SharePoint capabilities. In order to add a "follow" button on an SPFX web part, we'd need an API to access that.

    Related GitHub issue https://github.com/SharePoint/sp-dev-docs/issues/1689

    122 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →

  20. Programmatic way to configure search with CSOM

    There's currently no better way to configure search indexed and managed properties than export/import configuration. It's a huge pain when building search related apps and a black box, we need something better

    99 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 6
  • Don't see your idea?

SharePoint Dev Platform

Feedback and Knowledge Base

(thinking…)


SharePoint Tech Community

UserVoice Terms of Service & Privacy Policy