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. Open source the CSOM

    Please open source the CSOM code. This would allow community to add features like throttle support, .net core and others. Microsoft could update it from time to time to add new support for new APIs etc... also.

    It would allow the community to port it to platforms and runtimes that MS are not yet able commit time to doing.

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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 still committed on providing .NET Standard version of the CSOM, but are not planning to change the engineering processes to have CSOM released as an open-source version.

    This change would require significant changes on how the engineering processes work and would have impact on the agility of providing capabilities through CSOM and REST APIs. As we are investing heavily on the Microsoft Graph API surface, we are not planning to allocate resources to this work.

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

    233 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

    Webhook are supported in SharePoint Online and in SharePoint 2019 and even thought they’d absolutely also provide additional value on older versions, we cannot provide them without significant platform changes, which cannot be justified for the older versions.

  3. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    Closing as this is not an enhancement. It’s a potential issue in existing capability and reporting these in UserVoice is not the right way to get things sorted out.

  4. Not intuitive AT ALL. WHy so many steps to publish!?!!!

    Scrap the whole program and think through how to set up the functionality of Sharepoint. All I'm trying to do us publish my site and it is unnecessarily complicated. Nothing is intuitive, would take a month to tell you everything. Scrap all the code and rebuild the entire program from scratch...so it makes sense. Remove all of the "Overthinkers" from program engineering staff (have them work on something else). To many redundant, over thought out processes that make simple processes too complicated. I feel like I am forced to look through 10 drawers of beautifully detailed knives and I desperately…

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

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, there was no concrete or actionable input on this one.

  5. 103 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

  6. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

  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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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…

    551 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

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

    321 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

  10. 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…)
    Sign in with: Facebook Google
    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.

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

    286 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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 also working on new model for the content type management, which is not aligned with the classic content type hub design which should be soon available.

    We do apologize the delay around getting final conclusion on this submission

  12. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

  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

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

    153 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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.

  15. alan

    edfg

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not detailed enough for us to perform any action actions.

  16. Reverting to modern theme

    Hi,

    I changed a team site them to classic in SharePoint Online. I cannot find a way to revert back to modern look, I'm currently stuck with the classic look.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Site Scripts & Site Designs  ·  Flag idea as inappropriate…  ·  Admin →
  17. nothing

    Update framework

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 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 detailed enough for us to perform any action actions.

  18. I would like to embed an unsecure site page in my Sharepoint page

    I would like to embed an unsecure site page in my Sharepoint page

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

    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 is actually a security feature in the browsers which are blocking mixing https and http requests on the same page and we cannot solve that for you in SharePoint side.

  19. new-pnpsite

    Allow creation of modern sites using the cmdlet "New-PnPSite" using an Azure App ID. Currently this errors with "App-Only is currently not supported".

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

    App-only creation fo modern sites are not currently supported, so New-PnPSite cmdlet cannot also do this. This cannot be solved until the native API supports app-only, so we would rather recommend updating the request towards supporting this capability in general, not only specific with new-pnpsite.

  20. Scrap "client side web parts". You can do all this with normal javascript so why complicate it?

    Scrap client side web parts are just HTML and JavaScript but require the developer to install configure and use a whole suite of old hat wannabe command line software. This is a step back to the ancient art of command line cryptic development. Really, even notepad more advance then this.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    We do acknowledge that moving from classic JavaScript development to more structural industry standard patterns require some changes in your development process, but we absolutely want to standardize and move SharePoint development models aligned with what other platforms do. This changes might feel huge and even step backward, but it’s highly beneficial for the larger customizations. With the SPFx and client-side web parts you also get centralized control and governance, which is not there with random embedded JavaScript models like with Script Editor web part. We absolutely understand your feedback, but looking into adoption numbers (metrics of usage) of the SPFx, there’s really no reasons for us to turn back from this journey which we started a few years back.

← Previous 1 3 4
  • Don't see your idea?

Feedback and Knowledge Base