SharePoint
Feedback by UserVoice

SharePoint Dev Platform

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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Add Web.Recycle method to CSOM

    The Web class in the CSOM lacks the ability to send a web to the recycle bin. Currently it's only possible to delete a web by using Web.DeleteObject() which makes restoring from recycle bin impossible.

    Please consider adding a Recycle() method to the Web class.

    127 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Support .NET Core with CSOM

    Support .NET Core with CSOM

    2,329 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Just a quick update on this highly requested feature as we are happy to communicate clear progress on this submission.

    We are actively working on this with current estimate it being publicly released for production usage by end of June. We are just about to start internal validation of these components and if everything goes as planned there are no plans to further update the schedule.

    We do apologize the delay on getting highly requested feature released, but also looking forward on your input and feedback when the feature is available.

  3. Add Records.BypassLocks to the Client APIs

    CSOM contains very few methods compared to the Server Object Model equivalent relating to records management.

    There are only three methods; DeclareAsRecord, IsRecord and UndeclareAsRecord available to clients, compared to 25 methods in the Server Object Model.

    Many records management solutions for SharePoint that exist today as Full-Trust solutions make use of methods that are not included in CSOM, but a large number of these can be worked around with existing CSOM (for example, finding the declaration date of a record).

    One very important method that is missing however is Records.BypassLocks.

    This method is used to support a variety of…

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. 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,679 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Add API that checks if user is in group

    Right now there is no API to check that. If you add a security group into a SharePoint group, there is no way to check if the current user is a part of the SharePoint group: The user is not listed in the group.Users and the SharePoint group is not listed in the user.Groups. The 3 APIs that allowed to do this in full trust code are missing from CSOM so we need an alternative.

    97 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Content type remote event receivers

    Remote event receivers can currently, in SharePoint Online, not be added to content types (https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.client.contenttype_members.aspx). This makes it somehow tedious to catch events that are fired from items of a specific content type is added/updated/deleted. Having the possibility to add an event receiver to a content type would make this scenario easier to implement.

    97 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Provide the AddToCurrentScopeOnly in the RoleAssignment class for JSOM and CSOM

    The SharePoint "fine grain permissions" best practices document recommends using this method as a way to help prevent performance penalties when unique permissions are applied. However, we need this capability in JSOM and CSOM since AddToCurrentScopeOnly is currently only available for use on-premises using the server-side object model.

    45 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Add the possibility to set the Owner when creating a SharePoint Group using REST API

    It is currently not possible to set the Owner of a SharePoint Group using REST API or maybe I don't have right syntax...

    73 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Add the possibility to update a multi valued managed metadata column using REST API when updating an item

    When updating an item using REST API it is currently supported to update a managed metadata column if we'd like to add only one term.
    It would be very useful if we could update a managed metadata column to add several terms when updating an item using REST API

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Fix the REST API to return the value and not the Id when getting single value Managed Metadata field

    REST API should be fixed when getting single value Managed Metadata since it returns the Id instead of the actual value, which then requires another call to get the value. Without this you cannot show a list of items/docs with the single Managed Metadata value. Note that "Allow Multiple" Managed Metadata works fine as it returns a collection of actual values.

    For details see: http://sharepointificate.blogspot.com/2014/05/taxonomy-columns-sharepoint-2013-list.html

    143 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Global or tenant wide event receivers

    I'd like to see a reliable event receiver globall and/or tenant wide that fires when a site collection/site is created, updated etc. It should point to one or more external services.

    64 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add User Profile changes functionality to CSOM/REST

    When switching the development model from SharePoint server OM to SharePoint Apps (CSOM), there is one important feature that we are missing: the User Profile Changes API (http://msdn.microsoft.com/en-us/library/office/ms517376(v=office.14).aspx ).

    In an on premise environment there is still a way to implement this using server OM but in cloud environments there is no way to do it.

    Apparently the only way of synchronizing SharePoint user profiles or handle user profile changes in the App model is doing a brute-force full scan using CSOM, which is a much less performant approach. Is this the way how MS currently recommends to face…

    75 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Fix CSOM SiteCollection Creation providing Lcid

    When creating Site Collections through CSOM and providing an LCID. (For example 2067) an exception is thrown.

    [Quote]
    SiteCreationProperties.Template\r\nParameter name: Specified value is not supported for the SiteCreationProperties.Template parameter." is thrown at ExecuteQuery();
    [/Quote]

    The Exception is also not pointing in the right direction.
    1) It should be possible to create Site Collections providing the LCID
    2) When an Invalid Lcid is passed, the exception should point in the right direction.

    93 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. 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

    196 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Expose REST Endpoints in the SharePoint UI

    Here’s an idea I had a while ago based on a conversation I had with some of the other SharePoint MVPs: expose the REST endpoints and documentation right in the UI for those who have the appropriate permissions. It could be a little icon at the bottom of any page where there are relevant end points. All content is security trimmed anyway, so no one is going to see an endpoint they can’t use (though if they can fathom the docs they can know what endpoints there are available).

    Think about it:

    You’re on a List Settings page, and you
    62 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  16. Set internal site field name using REST API

    We use the following call to create a site field:

        $.ajax({
    
    url: appweburl + "/_api/SP.AppContextSite(@target)/web/fields?@target='" + hostweburl + "'",
    type: "POST",
    data: JSON.stringify({
    '__metadata': { 'type': 'SP.Field' },
    'FieldTypeKind': fieldType, 'InternalName': fieldInternalName, 'Title': fieldDisplayName, 'Group': fieldGroup, 'Required': fieldRequired, 'Hidden': fieldHidden
    }),
    headers: { "accept": "application/json;odata=verbose", "content-type": "application/json;odata=verbose", "X-RequestDigest": $("#__REQUESTDIGEST").val() },
    success: function (data) { console.log("Custom field successfully created");},
    error: function (err) { alert(JSON.stringify(err)); }
    })

    However, the internal name is not set to the parameter fieldInternalName. It seems that the internal name is also set to the display name and suffix. Would it be possible to specify the internal field…

    58 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Provide a means to do audience filtering for list items over REST APIs

    List items that have an Audience field attached should be audience filtered when retrieved via the REST API.

    For example, a list that has link items with the Audience field attached to target particular items at particular groups of people. If the REST APIs are used to retrieve items from this list, then the identity of the requesting user should be optionally used to filter the results based on audience.

    129 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. 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

    194 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
1 2 16 17 18 20 Next →
  • Don't see your idea?

Feedback and Knowledge Base