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. Open Source or at least Source Open the Yeoman Generator

    Plain and simple, I was hoping to see the source of the generator get released. The main reason is to see how things are done and how we can possibly improve on your process.

    I'm fine if you don't want to go full open source in the sense where you take PR contributions from the community (although I don't understand that reason), but at the very least you should do what's considered source open where you share the source code but don't accept PR's & contributions.

    21 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 Framework  ·  Flag idea as inappropriate…  ·  Admin →
  2. Make Localization accessible for QuickLaunch NavigationNode and WebPart titles

    Hi all,

    It would be really nice to add more support for localization in CSOM for SharePoint on-prem and online.

    In server side object model, it possible to localize NavigationNode (SPNavigationNode) using the TitleResource property like this:

            using (var site = new SPSite("https://UrlToMySharePointSite"))
            {
                using (var web = site.OpenWeb())
                {
                    var nodes = web.Navigation.QuickLaunch;
                    foreach (SPNavigationNode node in nodes)
                    {
                        node.TitleResource.SetValueForUICulture(new CultureInfo(1036), "My French Title");
                    }
                }
            }
    

    Same for WebPart Title. I've found a way to do this but don't have tested it (I tested it for NavigationNode but doesn't work) : http://sadomovalex.blogspot.ch/2015/09/localize-web-part-titles-via-client.html

    As we have a lot of…

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Warn when using preview SharePoint Framework features

    The latest version of the SharePoint Framework Yeoman generator contains a mix of features that are GA and preview features (for example connecting to MS Graph, web part connections, extensions). Whether the generated solution can be run in production depends on the features used to build the web part. With that, when bundling the project, the toolchain should warn of any experimental features being used in the project which would prevent the solution from being deployed to production tenants. This would help developers avoid deploying solutions depending on experimental features to production tenants, only to see the deployment fail.

    78 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We’re reviewing your suggestion. Like Pat already noted in the comments, we are looking into this one and hopefully can make this happen relatively soon. Thanks for your feedback!

  4. Extensions: Application Customizer - Loading JS Files in <HEAD> Tags

    The current architecture of the SPFx Extensions allow for us to populate "Placeholders", such as PageHead and PageFooter with content.

    If we need to load JS files though, be them stored within SP or externally, we would need to add external references into the <HEAD> tag of the page.

    We can use the current placeholders to dynamically update the <HEAD> tag, but this seems less then optimal.

    Classic UCA's allowed for multiple JS references, as well as the sequence in which they were loaded. (Ex: Load jQuery prior to loading a Utility JS file that is dependent on jQuery.)

    Replicating…

    31 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 Framework  ·  Flag idea as inappropriate…  ·  Admin →
  5. Extensions: Application Customizer - Additional Placeholders Requested

    Today we get PageHead & PageFooter... would like to have BEFORE/AFTER DIV's for QuickLaunch & PlaceholderMain

    Cross-reference:
    https://github.com/SharePoint/sp-dev-docs/issues/625

    429 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  6. 6 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 Framework  ·  Flag idea as inappropriate…  ·  Admin →
  7. onDelete Method for SPFx web part

    Provide an onDelete() method that occurs when a web part is deleted from a page. This will allow for the web part to remove any files related to the instance being deleted.

    See discussion on:
    https://github.com/SharePoint/sp-dev-docs/issues/289

    51 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! We like your suggestion and it’s being added to our backlog. We don’t have yet specific schedule for this, but item has been added to upcoming plans for the SPFx and since request does make sense and has been requested from other sources as well, this will be most likely implemented.

  8. pageContext.web.description and pageContext.user.id

    Web description and user id are both strangely missing from the page context. It would be great of they were available.

    13 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 Framework  ·  Flag idea as inappropriate…  ·  Admin →
  9. Access to re-use modern field render controls

    Modern lists/libraries have controls to render all fields in a modern view - specifically the hard ones like people picker and taxonomy picker.

    Exposing these as re-usable modules in a SPFx web part via for example react would be very useful. I'd be happy just having the field renderer, and I can deal with labels etc myself.

    49 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 Framework  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow for admins to specify CDN location when installing SPFx App package

    I'd like to have the option for an admin to 1) load upp the script and other resources in a customer owned or managed CDN location and 2) allow the admin to specify that location when adding the .sppkg file into the app catalog.
    This would allow for more flexible usage of SPFx applications and also allow enterprises to have better governance of the script resources - which would increase the adoption of SPFx and also allow ISV's to create more solutions.

    22 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    in the plans  ·  3 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  11. Expose NavigationNode.TitleResource in CSOM & JSOM

    You can already localize using SetValueForUICulture() for TitleResource or NameResource and DescriptionResource properties of Web, List, ContentType, and Field. What is missing is the ability to do this for NavigationNode and maybe CommandUIExtension to make localization complete.

    30 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. 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.

    46 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. 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

    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 →
1 2 21 22 23 25 Next →
  • Don't see your idea?

Feedback and Knowledge Base