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.

Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more

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. Extensions: Support Development in Local Workbench

    Today, application extensions in SPFx (command sets, application customizers & field customizers) can't be tested within either the local or SharePoint Online hosted workbench. This is a bummer and a big step backwards to such a cool aspect to the development story with SPFx.

    I get that you need a list to work with, but at a minimum, the workbench could have a static list with static data and no other functionality for us to test the customizations on.

    My wish is that Microsoft adds support to the workbench for extensions before GA.

    105 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.

    We have investigated this option and have concluded that only decent development experience for the SPFx extensions can be provided within the live sites, as instructed in the extension tutorials.

    As we are planning to deprecate the local workbench starting with the version 1.12.1, we are not looking into provide this feature in future.

  2. 103 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now. We are targeting our API efforts on the Graph API side and due to internal prioritize are not planning to allocate resources to new CSOM capabilities.

    If this capability is important for you in the Office 365 platform, we do recommend submitting a specific requests towards Microsoft Graph API changes to address the possible gap.

  3. 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.

    102 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.

    We are not looking into doing this operation on server side of SharePoint as it would require resolving the members based on Azure AD groups.

  4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now. We are targeting our API efforts on the Graph API side and due to internal prioritize are not planning to allocate resources to new CSOM capabilities.

    We are potentially looking into having Microsoft Graph API operations for the search configuration in the future, but we cannot currently share any ETA for this and capability will not be provided through classic CSOM APIs.

  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.

    This could be something which could be in the Microsoft Graph APIs, given the direction with Project Syntext and Topics, but no confirmation on the plans there.

  6. Add AlternateJsUrl to SPWeb in all SharePoint models to add JavaScript without customizing masterpage

    There is a nice property AlternateCssUrl, by which I can easly add CSS to my site without changing masterpage. I would also like to add JavaScript files (with inheritance) by UI or script, just as I can add CSS files trough AlternateCssUrl

    Please Please Please add it!
    This would provide a way to create branding without customizing SharePoint masterpages

    93 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your input around this. We have analyzed this request internally and due the direction where we are heading with modern experiences, we won’t be exposing this API in the CSOM side. There will be enhanced options to control branding for the modern team sites. With classic team sites, you should be able to achieve typical scenarios with UserCustomActions or alternatively with custom master pages. We do acknowledge that the API would be useful, but it could also open up additional challenges for the future.

  7. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Simplify CSOM for using w/Angular/Backbone/Sencha - for Real World Scenarios, use CSS than JS, overcome OData constraints (oriented to CRUD)

    All the things are related to SharePoint Online development:


    1. SharePoint CSOM model is too complex for using with leading technologies, such as AngularJS, Backbone, Sencha ExtJS and so on. And there is a lack of documentation for "built-in" CSOM/SharePoint JS API function, for example user name extraction from user field). You have to google a lot to find if anyone has found any solution how to solve it.


    2. There are lots of useless JavaScript that does a lot of functionality/processing that is available using pure CSS or native browser functionality (I'm not talking about HTML5 and CSS3 right now). For…

    89 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, we can’t really create unfortunately actionable items from this large list of requests. There are extremely valuable items in the text which we would love to get submitted as individual items, so that we can truly triage and address the challenges.

    What we are looking is specific actionable items in UserVoice for specific gaps. We can’t unfortunately address collection of items in single efficiently, since improvements will be also released gradually and not as a big bang.

    Your input has been absolutely acknowledged, but we’ll have to close this one and would rather request seeing if the specific items or topics have been already submitted as a one-by-one submissions or submit new items.

  9. 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...

    89 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. CSOM/REST - "open documents in the browser" (open in the client application, etc.) or allow "quick edit" (yes/now).

    Some list/library settings are available via CSOM. Others are available via the list property bag (although that approach is not desirable). However, there are even other advanced settings that don't appear to be accessible (read or write) via CSOM/REST. In particular, the advanced settings for "open documents in the browser" (open in the client application, etc.) or allow "quick edit" (yes/now).

    I'm looking at SharePoint 2013 when trying to do this, but I suspect the same problem occurs for SharePoint Online and SharePoint 2016.

    86 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Add CSOM Method to Release File Locks

    We need the ability to unlock files via CSOM (with an App Only token) via the SPFile.ReleaseLock method. The flow would be similar to what we can accomplish on-prem:

    $web = Get-SPWeb http://webUrl
    $list = $web.Lists['Documents']
    $item = $list.Items[0]
    $lockId = $item.File.LockId
    $item.File.ReleaseLock($lockId)

    This prevents needing to open support cases for long-lived lock files in scenarios where the end user is having connectivity issues causing long exclusive locks to be created, potentially locking the end user out of their own file.

    81 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Add-ins  ·  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…

    78 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.

    As we are focusing on the cloud in our engineering, this feature is intended to get replaced with Microsoft Graph user profile APIs, which expose different data objects than classic SharePoint User Profile service.

  13. Add modern webservice API functionality to supported API as graph

    There are two modern webservices used in SharePoint for getting followed sites, frequented sites, news posts, etc for the current user. As asked about on Github (https://github.com/SharePoint/sp-dev-docs/issues/1689) and as mentioned in this uservoice (https://sharepoint.uservoice.com/forums/329220-sharepoint-dev-platform/suggestions/34075903-api-support-for-followed-sties) a bunch of folks would like to have some kind of official support/usage for this. If this is not possible, we would like to ask to add these functions to Graph / SharePoint REST

    74 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.

    Followed sites is already supported in Microsoft Graph API.

    Frequent and news pots are not, but are being looked for, but as this item is bundling numerous items, we cannot track them separately. Those items are however looked for. To enable specific item tracking, please submit items one-by-one.

  14. Allow Excel Apps for Office to access cell address of selected cells

    Enhance the Office JS API to allow apps to read the cell address of selected cells so a better experience can be provided for users who need to see cell references made via their app. Top priority items should include:
    1. The ability to read the cell address of cells a user has selected when using addFromPromptAsync pop up. (e.g. Sheet1!$A$1). This is effectively the same address which shows within the addFromPromptAsync textbox currently.
    2. Ability to read cell references of any selected cell/cell range.

    This enhancement will be useful as currently apps can create a binding to a selection…

    74 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the feedback. As your feedback is related to Excel Apps, please submit your idea to the Office Excel User Voice forum.

    Thanks!

  15. Provide ability to deploy and activate master pages to the host web using the app model

    One thing that we still use Sandboxed solutions or FTC for is the deploying of branding assets such as master pages. Although, there are some hack-like approaches that you can use with CSOM, a more direct supported approach would be nice.
    It would be nice if the model would also set the master page on the host web as well since this is a common piece of code we write as a feature receiver as well.

    73 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Since you can upload and activate a master page on the host web using CSOM/JSOM/REST APIs, we consider this scenario to be possible with the existing APIs.

  16. Update SharePoint 2019 with the latest SPFx Drop

    Update SharePoint 2019 with the latest SPFx Drop. Most of the SharePoint Customers still have an OnPremises Farm. If you want customers to adopt this pattern it must be available in both environments. Staying on drop 1.4.1 in SP 2019 is the death of SPFx

    68 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.

    Let me provide some additional context of this to explain why we cannot do this. In short, it’s not just about supported SharePoint Framework version, it’s about dependency on all out-of-the-box web parts and UX implementation.

    We would love to provide updated SPFx support for SP2019, but this is unfortunately impossible due the server-side dependencies and restriction.
    SharePoint 2019 was created by forking SharePoint Online code while back. At the time the used SharePoint Framework for the out-of-the-box web parts and UX layer was SPFx 1.4.x with the related server-side dependencies, which is then setting the used SPFx version even for now. As SharePoint 2019 is using more than 2 years older out-of-the-box UX layer than SharePoint Online, there is unfortunately now way for us…

  17. 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
    65 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  18. Microsoft.SharePoint.Client.AuditQuery in CSOM

    It would be good to be able to query the Site Collection Audit data via the client-side object model.

    The current Audit Log Reports can serve a purpose, but the real power is being able to query the raw data and generate custom reports. This currently doesn't appear to be available in SharePoint Online and is only available for On-Prem via Microsoft.SharePoint.SPAuditQuery.

    62 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Provide the ability to create custom User Profile properties using CSOM/REST

    Customers usually creates multiple custom User Profile properties. And there is always a need to script this so that it can be repeated across the environments. Today, the only way is to create these using Web UI. This is a huge problem for customers who are dependent on a large number of custom user profile properties.

    61 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.

    We are targeting our API efforts on the Graph API side and due to internal prioritize are not planning to allocate resources to new CSOM capabilities.

  20. 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…

    59 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  • Don't see your idea?

Feedback and Knowledge Base