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.

I suggest you ....

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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…

    26 votes
    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 →
  2. 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.

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. 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.

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    As CSOM proxy assemblies will need to be 100% aligned with the server side APIs and they are automatically generated on daily basis in our build process, we cannot open-source them or it would have a severe impact on the agility of us shipping new features on weekly basis in SharePoint Online.

    SharePoint engineer coordinates, however, the open-source PnP CSOM extension work, which gives you the capability to extend the CSOM without impacting the oob CSOM lifecycle. This means that the community can add additional capabilities and features without negatively impacting the normal release process and agility of releasing new features.

    You can use PnP CSOM NuGet simply by adding that dependency to your project and it will add all needed dependencies, so it’s as simple as referencing oob CSOM NuGet, but you get more.

    PnP CSOM is currently used by 14k tenants on monthly basis and it has more…

  4. Add support to hide List View Command Set buttons

    In the classic experience it's possible to hide ribbon buttons and menu options in the ECB. In the modern UI this currently isn't possible.
    Please add support to also hide OOTB List View Command Set buttons and ECB items in the modern UI.

    In the Classic view this could be done by a Custom Action:

    <CustomAction
    Id="RemoveRibbonButtonLibrary"
    Location="CommandUI.Ribbon"
    RegistrationId="101"
    RegistrationType="List">>
    <CommandUIExtension>
    <CommandUIDefinitions>
    <CommandUIDefinition Location="Ribbon.Library.Actions.ExportToSpreadsheet" />
    </CommandUIDefinitions>
    </CommandUIExtension>
    </CustomAction>

    But this currently doesn't work for the Modern UI.

    22 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 →
  5. More links to footer / fat footer

    It would be really nice to get more links to the footer to be able to create this kind of "fat footer". Current footer only allows 8 links/headers, but we would love to see footer where you:
    1. can choose the layout (columns/rows)
    2. can have header (styled/bolder/font size) with or without link and the add n-number or links below it.

    So something like this (3 columns x 2 rows example):

    HEADER1 | HEADER 2 | HEADER 3
    link1 link1 link1
    link2 link2 link2
    link3 link3 link3

    HEADER4 | HEADER 5 | HEADER 6
    link1 link1 link1
    link2 link2 link2 …

    22 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 →
  6. Extensions : application customer include a left-nav placeholder which will allow options to hide, pane or customise

    there are many requests for leftnav customisation options which often come in business requirements. Nav is always something that users get quite excited about.

    why not combine this with the work being considered on new placeholders for the application customizer

    include a simple script way of specifying that you want

    no left hav
    narrow left nav with icons only (like VS code)
    standard left nav but in flyout pane to conserve space(like modern details pane)
    fully customised and specified in extension

    22 votes
    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 →
  7. Parameter for passing specific Site Design in Modern Team site Creation

    While creating the Modern communication site programmatically through Rest API/ Graph API there is a parameter available to choose the site design.

    Title = "title
    Description = "description
    AllowFileSharingForGuestUsers = false
    Classification = "classification"
    SiteDesign = CommunicationSiteDesign.Topic

    But while creating the modern team site programmatically there is no option to choose the Site Design, by default it is picking up the default Site Design. Even though we can create multiple site script and site design for Teams site, we are not able to specify a site design at the time of provisioning the Group.
    Is there any possibility to choose…

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. 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…

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. 21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Updating existing projects to newer SPFx builds

    When building an SPFx project on current version of SPFx build, it is very hard to upgrade this to the latest SPFx builds that are coming out after while still enjoying all the new features that are a part of that latest version.

    This includes breaking changes that prevents the code from compiling, but also more importantly: added configuration options and features to the different config files that are a part of the project, or changes to the schema that adds a few more options that are a part of the new SPFx build.

    These changes today have to be…

    21 votes
    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 →
  11. Add CSOM API to choose content database and quota when creating site collections

    In the April 2014 Cumulative Update for SharePoint 2013 (released on 7th of May 2014) you published the possibility to create site collections remotely via the CSOM API.

    Till today it's not possible to choose a desired content database where the site collection should be stored in or to configure a quota template.

    Senior Program Manager Vesa Juvonen from Microsoft wrote a detailed blog article about this topic and received a broad response from the community where many people need these missing features.

    See here: https://blogs.msdn.microsoft.com/vesku/2014/06/09/provisioning-site-collections-using-sp-app-model-in-on-premises-with-just-csom/

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Extensions: AppCustomizer - Register Event Listeners in Modern Page DOM

    It would be great if there was a controlled way to leverage AppCustomizers to register event listeners in modern pages. This capability will empower enterprise developers to create sophisticated auditing and usage reporting solutions for SPO. e.g. Tracking how many times a given user has downloaded files by tracking the “click” event on the file download button and coupling that event with page context information.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  13. Need more placeholders for spfx extensions

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

    We also need to display properties of a folder in a document library on top of the document library name or next to the document library name or some best place to show the document library folders information which can also be on top of the document library fields.

    Above feature can be easily achieved through CEWP and jquery in the classic experience.

    20 votes
    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 →
  14. Add support in CSOM to modify the CustomScriptSafeDomains settings for a site

    Support was added in March 2018 to read the CustomScriptSafeDomains settings for a site - we'd like the possibility to modify this setting through the CSOM API - not methods are currently available to modify this settings through code.

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Make SPFx projects compatible with TSLint VSCode extension

    Make SPFx projects compatible with TSLint VSCode extension by either moving the tslint.json file to the root folder or by creating a new tslint.json at the root that instructs the VSCode extension to look for rules on the config folder

    18 votes
    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 →
  16. Workbench: allow to change size of the canvas to match real pages

    It'd to have a button in the workbenches (local, online) to allow us to apply the "layout" (different boxes sizes, flowing behavior, etc) of a team site or a communication site so we can double check rendering of our webparts work well with production dimensions, flowing behavior etc...

    Today the only way to try to mimic that is the tablet mode in the workbench, the browser debug tools or just resizing the window. This offers a poor experience and doesn't guaranty me my webpart is in the same rendering context.

    17 votes
    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 →
  17. Expose search managed properties and result sources through REST and CSOM.

    This will enable developers to build richer property searching applications.

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Upon deleting a site collection redirect user to other URL

    HI Team,

    Can we get a feature where a user will be redirected to some other URL(Custom) instead of SharePoint default URL once the site is deleted from any place ?

    Thanks & Regards,
    Pavan.

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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.

    17 votes
    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 →
  20. Field Customizer: expose List Item data to TypeScript API

    Currently there are some problems with getting List Item data from API for Field Customizer: event.fieldValue that is available in onRenderCell event sometimes contains not what actually expected or what is not enough.
    For example, Hyperlink or Picture field has 2 properties that should be available in Field Customizer: url and descripbtion, but only url is available now.
    Of course, most of the needed values could be requested via REST but it would slow the rendering for the column significantly.

    Given that the information is already preloaded on the page, ideally this information should be exposed via an SPFx TypeScript…

    17 votes
    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 →
  • Don't see your idea?

Feedback and Knowledge Base