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

    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.

  2. Calling list.asmx in sharepoint hosted app

    Due to cross domain it won;t call list.asmx service. in app please allow calling list.asmx request

    1 vote
    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 →

    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

  3. SharePoint App/Add-In Development for On Premises - include Workflows as Integrated within the App like you allow in Office 365

    Today, when I create a new SharePoint Add-In (App), I cannot include the SharePoint 2013 workflow within my app (On Premises only). I see there is a workaround for Office 365 Add-Ins, but we are not in the cloud yet. I also see Visual Studio 2015 has a setting for Integrated App (true/false), but not sure if this will work on premises yet (will try this out soon). I need the ability to include my custom SharePoint 2013 Declarative workflow as part of my custom add-in (app) for on premises. Bill Baer stated that my app will work the same…

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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.

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

  6. 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…)
  7. Allow working with Display Templates directly in Visual Studio

    It would be great to have support for working with Display Templates in Visual Studio, e.g. intelli-sense, deployment process etc. available. As an example, one could connect to a SharePoint solution and work directly on Display Templates, instead of having to go all the way through the designer.

    24 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 →
  8. Release current Office Web Widgets for production scenarios

    It's been almost a year since the Widgets were presented as an experimental module. Is it possible to release at least the two widgets presented (List View and People Picker) for using in production environments?

    We can think of huge potential for these components in commercial provider-hosted Apps (even with the exact set of features that they are offering right now), but if we are not guaranteed actual support for them, we really do not see the value of investing on solutions that use them.

    45 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. We are no longer investing on these components, but would suggest to have a look on the Office UI Fabric Components, which provides similar capabilities as these.

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

  10. 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…)
  11. 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

    205 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Please create a MY App Launcher Chrome Control

    As a Sharepoint Developer I have used a lot the chrome control in Sharepoint Apps, however with the new App Launcher and My Apps Page, I would suggest that Microsoft creates an "app launcher chrome control", a piece of code we can "copy/paste" in our webforms/mvc/js apps that will show automatically the Apps Launcher.

    I believe this will be a great way to navigate between LOB Apps that we create in the Offce 365 Platform.

    Thank you

    42 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint Add-ins  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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.

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

    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 looking into making this capability potentially to happen in upcoming modern pages API through Microsoft Graph, but are not planning to provide CSOM API for it.

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

    157 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Provide the JSOM API to create SharePoint Site Collections (Tenant Object as CSOM C# has)

    In the CSOM C# object model we have the Tenant object that allow us to create Site Collections and do other operations over the Tenant. There is a lack of this piece of the API in the JSOM JavaScript object model. Please extend the JavaScript API with this functionality.

    BTW - I would suggest to add a new category as "JSOM Gaps"

    106 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 looking into possibly opening up admin REST APIs in the future, but do not have exact timeline for this right now.

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

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

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

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

  • Don't see your idea?

Feedback and Knowledge Base