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. Add User Profile changes functionality to CSOM/REST

    When switching the development model from SharePoint server OM to SharePoint Apps (CSOM), there is one important feature that we are missing: the User Profile Changes API (http://msdn.microsoft.com/en-us/library/office/ms517376(v=office.14).aspx ).

    In an on premise environment there is still a way to implement this using server OM but in cloud environments there is no way to do it.

    Apparently the only way of synchronizing SharePoint user profiles or handle user profile changes in the App model is doing a brute-force full scan using CSOM, which is a much less performant approach. Is this the way how MS currently recommends to face…

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

  3. Target Audience property for SPFx web parts

    I understand the SPFx web parts are running in the user’s context. It would be helpful if the new framework has the target audience property

    78 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 →
  4. 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 →
  5. Add CSOM Method to Release File Locks

    We need the ability to unlock files via CSOM (with an App Only token) via the SPFile.ReleaseLock method. The flow would be similar to what we can accomplish on-prem:

    $web = Get-SPWeb http://webUrl
    $list = $web.Lists['Documents']
    $item = $list.Items[0]
    $lockId = $item.File.LockId
    $item.File.ReleaseLock($lockId)

    This prevents needing to open support cases for long-lived lock files in scenarios where the end user is having connectivity issues causing long exclusive locks to be created, potentially locking the end user out of their own file.

    75 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Add-ins  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add modern webservice API functionality to supported API as graph

    There are two modern webservices used in SharePoint for getting followed sites, frequented sites, news posts, etc for the current user. As asked about on Github (https://github.com/SharePoint/sp-dev-docs/issues/1689) and as mentioned in this uservoice (https://sharepoint.uservoice.com/forums/329220-sharepoint-dev-platform/suggestions/34075903-api-support-for-followed-sties) a bunch of folks would like to have some kind of official support/usage for this. If this is not possible, we would like to ask to add these functions to Graph / SharePoint REST

    73 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. SharePoint Add-in Document Library in AppWeb Does not render PowerPoint

    SharePoint Add-In AppWeb Document Library allows to create PowerPoint however once it is created, you click on the PowerPoint and it does not render. it throws an error. Word, Excel works fine however this might be an issue with OWA Office Web Apps and PowerPoint Online. This issue started appearing from Jan 2018 across all Office 365 tenants. Is there any resolution from Microsoft on this? https://techcommunity.microsoft.com/t5/SharePoint-Developer/Can-t-open-PowerPoint-files-from-a-Library-inside-an-Add-In/m-p/163739#M4419

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

    67 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 Webpart - Have custom group in Modern Pages

    Currently there are no ways we can have a group created for custom SPFx webparts developed. We have to use the existing groups mentioned here, https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/guidance/simplify-adding-web-parts-with-preconfigured-entries#predefined-modern-groups. Need to have ability to have custom groups for Webparts

    66 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. Expose REST Endpoints in the SharePoint UI

    Here’s an idea I had a while ago based on a conversation I had with some of the other SharePoint MVPs: expose the REST endpoints and documentation right in the UI for those who have the appropriate permissions. It could be a little icon at the bottom of any page where there are relevant end points. All content is security trimmed anyway, so no one is going to see an endpoint they can’t use (though if they can fathom the docs they can know what endpoints there are available).

    Think about it:

    You’re on a List Settings page, and you
    65 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 →
  11. Global or tenant wide event receivers

    I'd like to see a reliable event receiver globall and/or tenant wide that fires when a site collection/site is created, updated etc. It should point to one or more external services.

    64 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  12. Field Customizer: Ability to call ootb render method

    Allow to call out of the box render for cell in custom field customizer.

    Use case:
    based on user permissions render out of the box LinkTitle cell or custom copmonent with additional logic.

    This scenario is needed for all types of fields that are rendered as complicated HTML, not just text (LinkTitle, User or Group fields, etc.)

    62 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  13. Set internal site field name using REST API

    We use the following call to create a site field:

        $.ajax({
    
    url: appweburl + "/_api/SP.AppContextSite(@target)/web/fields?@target='" + hostweburl + "'",
    type: "POST",
    data: JSON.stringify({
    '__metadata': { 'type': 'SP.Field' },
    'FieldTypeKind': fieldType, 'InternalName': fieldInternalName, 'Title': fieldDisplayName, 'Group': fieldGroup, 'Required': fieldRequired, 'Hidden': fieldHidden
    }),
    headers: { "accept": "application/json;odata=verbose", "content-type": "application/json;odata=verbose", "X-RequestDigest": $("#__REQUESTDIGEST").val() },
    success: function (data) { console.log("Custom field successfully created");},
    error: function (err) { alert(JSON.stringify(err)); }
    })

    However, the internal name is not set to the parameter fieldInternalName. It seems that the internal name is also set to the display name and suffix. Would it be possible to specify the internal field…

    61 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Support sub-menu options for List View Command Sets

    Listview CommandSet extension - Should be able to create custom commanbar button in the listview commandbar with sub-menu options like it is available for default buttons on the command bar.

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

    61 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 Site Collection App Catalog location be configurable

    We live in a tenant where we have over 25 different companies. When it comes to customizing and supporting the tenant catalog is too broad, but the site collection catalog adds support nightmares with syncing and managing the apps and installs in each one. It would be great if the site collection admin could choose an additional Site Collection app catalog to pull from. This would allow for us to manage company specific apps in a Company site collection catalog much like the tenant catalog while still getting site specific catalog items from the site collection catalog. In this model,…

    59 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. Flicker Issue when loading Branding Artifacts (css, js etc.) using SPFx Extension in Modern SharePoint Site

    Need help for the following scenario wherein any modern page that gets displayed shows a flicker of the default SharePoint page for 1-2 seconds before the actual page with branding is displayed.
    Details:
    We are facing an issue regarding the user experience in SharePoint Modern sites. For Branding, we have used SPFx Application customizer aka extensions to inject custom styles. With this implementation, we are facing a flicker because extension takes fractions of seconds to load itself. In the meantime, OOB page appears first and then extension starts loading.
    Is there any way to load SPFx extension before SharePoint page…

    56 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 →
  18. 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 →
  19. 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
    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 →

    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.

  20. Ability to deploy MS Flow Definition through .sppkg, similiar to how we can provision list and libraries.

    The deployment of SPFx components along with associated list and attached flow can be done with-in a single package so that minimum exclusive configuration is required for any developed solution.

    51 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