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. Improve Popup Behavior when consuming APIs secured with Azure AD within the SharePoint Framework

    When using the AadHttpClient within a SPFx WebPart, a popup appears that is currently necessary to facilitate authenticate to Azure AD (part of ADAL JS). While this is understandable if the user needs to supply additional authentication components, if the user has the necessary rights to the Azure secured API, no popup should be presented.

    Scenarios where this behavior is not acceptable:
    - Pages with multiple third party data sources (user is bombarded with popups)
    - High traffic landing pages (like corporate home pages) where look & feel are crucial

    Documentation on behavior:
    https://docs.microsoft.com/en-us/sharepoint/dev/spfx/use-aad-tutorial

    GitHub Issue relating to this:
    https://github.com/SharePoint/sp-dev-docs/issues/1471

    11 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 →
  2. "FieldValues..." in REST API gives double-encoded field names

    As reported by Shai Petel in github (https://github.com/SharePoint/sp-dev-docs/issues/1141), column names with non-ASCII characters or "special" characters (i.e. those that get encoded) are being double encoded by the REST API in the FieldValues... properties (this includes FieldValuesAsText, FieldValuesAsHtml, and FieldValuesForEdit).

    For example, create a column called "Français" in a list with Title "Test" and call the following REST request: /api/web/lists/getbytitle('Test')/items?$expand=FieldValuesAsText,FieldValuesAsHtml,FieldValuesForEdit. in the response given the field's internal name is properly shown in the field values as "Franx00e7ais", but is shown as "Franx005fx00e7x005f_ais" in all of the "FieldValues..." properties.

    This makes it very difficult…

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

    Support for PublishingPageImage & PubliblishingPageIcon in REST API. Now we need two API requests to get the columns.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →
  4. Fix the issue regarding sharepoint list column name

    Sharepoint will not be able to issue the xml list of lists when one of the column is named with symbols only such as "***" or "-" . If this is causing issues they should either be resolved or the column should not permit being named in this way.

    thanks

    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 →
  5. 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=&quot;RemoveRibbonButtonLibrary&quot;
    
    Location=&quot;CommandUI.Ribbon&quot;
    RegistrationId=&quot;101&quot;
    RegistrationType=&quot;List&quot;&gt;&gt;
    &lt;CommandUIExtension&gt;
    &lt;CommandUIDefinitions&gt;
    &lt;CommandUIDefinition Location=&quot;Ribbon.Library.Actions.ExportToSpreadsheet&quot; /&gt;
    &lt;/CommandUIDefinitions&gt;
    &lt;/CommandUIExtension&gt;

    </CustomAction>

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

    54 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. Allow spfx webparts to be added to classic publishing pages

    When trying to add SPFX webpart to classic publishing page, sp.runtime.js is trying to load twice which is causing a conflict and resulting in the page to breaking, I have tried a few workaround but hasn't solved my issue.

    18 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. Write to Web Property Bags

    The ability to both read and write to the various property bags would be very helpful. Currently it's possible to read from a web property bag, but not to write. It'd be even better if the other property bags supported this.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Users with SharePoint Admin roles should be able to add (and remove) Site Collection App Catalogs

    A user that has been granted the role SharePoint Admin should have administrative rights over the site collections. This should include being able to add (and remove) site collection app catalogs. This should be particularly true when that user is also the site collection administrator.

    The error message says "Must have Manage Web Site permissions or be a tenant admin in order to add or remove sites from the site collection app catalog allow list"

    Site Collection administrators have manage web permissions, minimally, yet are unable to do so. This doesn't make sense. This was reported as a bug but…

    42 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 →
  9. Make it possible to completely hide an SPFx web part at runtime

    It should be possible to create a web part that will decide to hide or show at runtime -- for example, when you want to say "Don't show this webpart if there are no results", and it should show no spaces or gaps in the page.

    Although it is possible with CSS to approximate this, there is always a gap in the page.

    I would suggest that you make the web part visible in Edit mode, regardless of its settings, so that page editors can access the web part settings.

    28 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 →
  10. SharePoint Extensions on Classic Sites

    Please, make it possible to use SharePoint Extensions on Classic sites in order to use common components throughout the tenant. A good example is the Footer, we want to use the same footer so we don't have to build two different components in two different technologies.

    2 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. 7 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 →
  12. Provision SPFx (.sppkg) add-ins on a site on-premise

    ALM API is available now for SPO. SPFx now is available for SP2016 on-prem, too, since Feature Pack 2. But still there is no way to provision .sppkg files (either form local disk or from AppCatalog) on a site. Please, add this. There is no migration path from provider-hosted add-ins to SPFx add-ins for our applications now, because method LoadAndInstallApp() which worked for .app files does not work for .sppkg files.

    29 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 →
  13. Create Retention polices /Labels with REST API

    Create Retention polices /Labels with REST API

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →
  14. Modern page extensions

    It would be great to add commands to the command set of a modern page, with similar events to list view extensions e.g. onListViewUpdated > onPageUpdated, and onExecute.

    The API should enable easy and reliable access to important page information like field data, published state, whether it is promoted as news, etc.

    76 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. 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 →
  16. Allow to add custom Styles in the HEAD section

    Adding custom styles in HEAD section is a powerfull way to let the page content be imediately displayed in reasonable fashion, if required.

    Adding or changing elements after the page is loaded may cause a flickering effect that is not optimal is some cases.

    With custom styles on the HEAD section, it will be possible to add "loading indicators" for async components or change basic styles, like fonts and colors, that would not feel so good if initially loaded wrong.

    Example: Given the default navbar has a black background and the custom branding for a site has transparent background. It…

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

    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 →
  18. Field Customizer: call onRenderCell when switching between views

    Now onRenderCell is not called if user switches between views using drop down in List Command Bar and the list item is presented in both views.
    I understand that this is done for performance improvements but it leads to issues if there is a necessity to display the field in different ways based on a view.

    For example, voting or rating. In one view I want to see the results only (read-only) and in other view I want to be able to vote (rate) or change my previous selection.
    Another example - sales comparison. One view is needed to color-code…

    7 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 →
  19. Enable loading indicator method (displayLoadingIndicator) for CommandSets

    The SPFx web part interface defines methods for displaying and clearing a standard loading indicator (in IClientSideWebPartStatusRenderer), however this does not exist in equivalent BaseListViewCommandSet class. Or anywhere else I can find.

    Currently I'm using some garbage jQuery DOM manipulation to suffice but it would be great if we could do a simple:
    this.context.statusRenderer.displayLoadingIndicator(...);
    To show the standard SP page loading indicator during async operations, something that every one of my cmd-sets have.

    Thanks,
    Martin

    7 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. PowerShell CSOM (Sharepoint Online) / PNP Powershell - Rootfolder.storagemetrics properties loading as zero

    When navigating CSOM using PowerShell or PNP cmdlets to expose rootfolder.storagemetrics properties (totalsize, totalfilestreamsize, totalfilecount, lastmodified) in SharePoint Online, these are all loading as zero for site collections, sites, list/libraries, subfolders, etc (even after being loaded properly). These same properties are successfully exposed through REST API as well as using the SPO Client Browser application.

    Example code:
    PNP Powershell:
    Connect-PnPOnline https://tenant.sharepoint.com/
    $web = Get-PnPWeb -Includes RootFolder, RootFolder.StorageMetrics
    $web.RootFolder.StorageMetrics

    Return

    LastModified : 1/1/0001 12:00:00 AM
    TotalFileCount : 0
    TotalFileStreamSize : 0
    TotalSize : 0
    Context : OfficeDevPnP.Core.PnPClientContext
    Tag :
    Path : Microsoft.SharePoint.Client.ObjectPathProperty
    ObjectVersion :
    ServerObjectIsNull :
    TypedObject : Microsoft.SharePoint.Client.StorageMetrics

    End

    Powershell…

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  • Don't see your idea?

Feedback and Knowledge Base