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. Allow us to develop custom modern forms with custom edit experience

    We would like to be able to create an SPFx form and associate it with the List/Content type Disp, Edit, New form so that no matter how a user finds a list item (search, OOB list view, custom list view, etc) they see our custom form. Currently our only option is to create a completely disconnected experience in which we write a custom list view that points to custom form pages.

    Alternatively support field customizers with edit model to enable custom field editing experience.

    1,404 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    31 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  2. When creating an SPFx Extension for a custom header, provide a configurable property that allows the composite header to be hidden

    When developing a SharePoint Framework Extension to display a custom header and/or footer, the SharePoint Composite Header can be very redundant to the custom header.

    The Composite Header (css classname is 'ms-compositeHeader'), is what SharePoint provide out of the box and includes the square site logo, site name and navigation.

    When creating your own custom header that includes all of these things and possibly more, the existence of the Composite Header is redundant and can be confusing for users...(Ex: redundant navigation).

    While CSS can be used to hide this, such a technique is not playing within the rules of only…

    602 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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

    358 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add support of SharePoint Framework solution packages to the AppSource Store

    The latest adjustments in the Microsoft Store police allows store's add-in to works with conjunction with another add-in that is available only from the provider. The solution package (.sppkg) build with SharePoint framework is not classified as 'add-in'. Thus, we cannot add add-in in the Store that depend on SPFx solution and there is no way of delivering customizations to the modern page.
    I can offered two options for solving this issue: 1) Adjustment of point 4.18 (https://docs.microsoft.com/en-us/office/dev/store/validation-policies#bk_4) from the Store policy to allows SPFx modifications 2) ApPSource store to start allowing .sppkg solution packages to be added

    310 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow to use Office UI Fabric Icons and other fonts as Command Set icons

    It would be great if we are able to use font icons instead of url to images for Command Set extensions buttons icons.
    This allow 3d party extensions look more aligned with 1st party (same style, same icon color)

    209 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  6. Extensions: Property Pane / SideBar Placeholder (Right)

    Please provide a well-known placeholder for the property pane or better a similar placeholder that let us create a sidebar.

    Having this ability would let us create powerful sidebars/toolbox extensions. This would be a super cool enhancement!

    207 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 →
  7. Provide support for LivePersonaCard in 3rd-party solutions

    The LivePersonaCard control, which renders a user's full profile card, can be loaded in a SPFx solution with LoadByComponentId. However, it is unclear whether this will be supported in the future.

    The PnP reusable controls has a Pull Request to provide developers with a LivePersonaCard control, but it is currently in holding pattern until it can be confirmed that LivePersonaCard (and LoadByComponentId) will be supported.

    Please empower 3rd party developers to build rich user-aware SharePoint solutions by providing solution for the live persona card.

    Cross-reference: https://github.com/SharePoint/sp-dev-fx-controls-react/pull/353

    197 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow extending SharePoint Admin Center using SPFx

    It would be nice to have the ability to extend some of the functionality in the SharePoint Admin Center. Specifically, the ability to deploy SharePoint Framework Web Parts into the Admin Center (via an App Page?). Currently, the community builds lots of SPFx Web Parts to fill the gaps in the Modern UX.

    Such Web Parts include:
    Theme Manager
    Site Design Studio/Manager

    These are SPFx solutions that have been built to help better manage our environments through a UX experience (as there isn't one via First Party). It would be nice to have a centralized location where these SPFx solutions…

    165 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 →
  9. SPFx Key/Value Pair Properties that support Read/Write

    Provide a SharePoint Framework mechanism/API that allows for Site or Site Collection Read/Write of Key/Value pair properties for use in SPFx related configuration and customizations. Similar to how the property bag was used in classic.

    One use case is for storing configurable properties or even user personalization configurations written and read by an SPFx solution.

    This is one of many uses cases that would make this feature valuable, so in addition to your vote, please feel free to comment with additional ways in which this feature could provide additional value.

    150 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    thinking about it  ·  4 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  10. Enterprise Deployment of SharePoint Framework Apps in an On Premise Platform

    There is currently no good way to do enterprise level automated deployments of an SPFX addin into a SharePoint 2016 on Premise environment..

    Consider a case where there are 1000 site collections and we would need to deploy an SPFX app to all sites automatically. Currently there is no way to perform this deployment in an automated fashion. It is not possible through powershell, csom, c# or in an administrative UI.

    Having this ability would solve a large hole in capabilities with SharePoint Framework

    140 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 →
  11. Web parts: Allow them to be unit testable

    Trying to unit test web parts results in an error 'Cannot find module "@ms/sp-telemetry"'. This can be due to using SharePoint dependencies e.g. 'SPHttpClient' when creating the React component. This totally blocks being able to unit test web parts, please fix this.

    '@microsoft/sp-build-web' Seems to have been updated to remove the previously included testing modules, these do not have to be added back in, to resolve this issue, as we are able to find the most suitable testing modules to replace these.

    This issue has been reported by other users:
    https://github.com/SharePoint/sp-dev-docs/issues/526
    https://github.com/SharePoint/sp-dev-docs/issues/1076
    https://github.com/SharePoint/sp-dev-docs/issues/243

    132 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 →
  12. Extensions: Application Customizer get page all components data (List, Documents, Search etc..)

    Provide a way to get data about all components that present on page in ApplicationCustomizer like SearchBox, Search, Documents Library, Lists, Navigation bar etc.

    The idea is to have full control on user interaction with components.

    In example I want to make an additional action when user clicks on folder, file, list item, navigation item, search result item etc...

    Ideally to have access to domElement and data model of component.

    106 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 →
  13. Create SPFx webparts inside or from another SPFx webpart or extension

    As described in https://github.com/SharePoint/sp-dev-docs/issues/3110

    Untill SPFx version 1.4.1 there was an option to use the ClientSideWebPartManager to create webparts from another webpart. Currently we are working some time already on a custom 'widgetzone' with an easy dragging and dropping grid layout (Muuri, https://haltu.github.io/muuri/), user zones and a lot of other awesome stuff which isn't supported by the default SharePoint grid. (which is off course understandable)

    Currently I am not seeing another path to make this possible, so for now we have to stick on the SPFx 1.4.1 release. I do understand this is something not many companies will encounter,…

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

    99 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add --nobuild flag to gulp serve

    Observed behavior

    When using a monorepo manager, like for example @microsoft/rush, the rush build command bundles all projects which are referenced in the monorepo - including SPFx projects.
    When running gulp serve in (one of) the SPFx project(s), the bundle gulp command rebuilds the project. This is an unnecessary step, which would be nice if we could disable.

    Proposed solution

    Add a --nobuild flag support to the gulp serve command so we can start the local web server without rebuilding the SPFx code.

    80 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 →
  16. Allow calling an HTTP-triggered Flow after installing SPFx solution in a site

    When creating sites using a site design (recipe), one of the available verbs is calling an HTTP-triggered Flow to perform some additional configuration on the newly created site.

    When installing SPFx solutions in a site, we should similarly be able to specify an HTTP-triggered Flow to be called as a part of the installation process. This would not only allow developers to provision configuration beyond what's currently supported with Feature XML, but also create a consistent development experience across the different workloads (site designs vs. SPFx).

    78 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 →
  17. SpFx Hide page until WebParts Load

    Simply hide the page canvas until all SpFx WebPart promises have resolved for modern sites

    This would conceivably
    1. Improve page load performance by not forcing the browser to display several loading gifs/fading animations at the same time
    2. Improve user experience by displaying a complete page to the user rather than the page "jumping" constantly during the first 3-10 seconds of loading
    3. Allow developers to add minor CSS updates to the page prior to render using the SharePoint Framework without noticeable "jumping"

    77 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 →
  18. 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.

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

  19. Office UI Fabric as web components

    Office UI Fabric is an awesome library, which contains a lot of components and UI elements. It's a great library to build UI experiences for SharePoint and Office 365.

    The downside is, that the most feature-rich version of the library built with React. If you want to use this library, you should use React without much options. There is Office UI Fabric JS out there, however it's not actively supported and developed as React one. Also it's difficult to reuse it in other frameworks. Office UI Fabric is must-have library in almost any SharePoint Framework solution.

    SharePoint Framework has framework-agnostic…

    64 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 →
  20. Implement support to invalidate custom property pane controls

    At the moment custom property pane controls cannot invalidate the whole property pane. This means if you enter an incorrect value for your custom input, the property pane will still apply it (or the apply button will be enabled).

    It would be great to have a way to make it possible to invalidate the property pane like the OOTB property pane controls. This would have a huge benefit for all the controls of the @pnp/spfx-property-controls (https://github.com/SharePoint/sp-dev-fx-property-controls) project which is used in a lot of projects.

    More details for this can be found in this issue on Github: https://github.com/SharePoint/sp-dev-docs/issues/3440

    58 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 →
← Previous 1 3 4 5 6 7 8
  • Don't see your idea?

Feedback and Knowledge Base