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. Content type remote event receivers

    Remote event receivers can currently, in SharePoint Online, not be added to content types (https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.client.contenttype_members.aspx). This makes it somehow tedious to catch events that are fired from items of a specific content type is added/updated/deleted. Having the possibility to add an event receiver to a content type would make this scenario easier to implement.

    81 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  3. Enable ListItem SystemUpdate via REST

    Allow REST clients to update list items a la SystemUpdate. That is, REST clients should be able to update list item metadata without creating a new version and without affecting system columns like authors and timestamps. The same idea for CSOM was recently implemented and I'm puzzled why the REST API is always left behind.
    The CSOM idea:
    https://sharepoint.uservoice.com/forums/329220-sharepoint-dev-platform/suggestions/15147093-enable-listitem-systemupdate-via-csom

    79 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. 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…)
    Password icon
    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!

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

    75 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. 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).

    74 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add Web.Recycle method to CSOM

    The Web class in the CSOM lacks the ability to send a web to the recycle bin. Currently it's only possible to delete a web by using Web.DeleteObject() which makes restoring from recycle bin impossible.

    Please consider adding a Recycle() method to the Web class.

    71 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. 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"

    70 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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

    68 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  SharePoint Add-ins  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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.

    63 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  11. Microsoft.SharePoint.Client.AuditQuery in CSOM

    It would be good to be able to query the Site Collection Audit data via the client-side object model.

    The current Audit Log Reports can serve a purpose, but the real power is being able to query the raw data and generate custom reports. This currently doesn't appear to be available in SharePoint Online and is only available for On-Prem via Microsoft.SharePoint.SPAuditQuery.

    62 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Provide the ability to create custom User Profile properties using CSOM/REST

    Customers usually creates multiple custom User Profile properties. And there is always a need to script this so that it can be repeated across the environments. Today, the only way is to create these using Web UI. This is a huge problem for customers who are dependent on a large number of custom user profile properties.

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

    59 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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…

    57 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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,…

    57 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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…

    54 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. 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,…

    53 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  19. Official documented Api needed to fetch modern Pages View count

    SharePoint modern pages Social bar View count apparently does not use Search Managed property ViewLifeTime or ViewsLifeTimeUniqueUsers. Fiddler traces shows that some Internal Apis are used to fetch modern pages social bar view count. It would great if Microsoft release Public documented API so that custom SPFx web parts/extension in need of modern page view count, could utilize the API

    49 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  20. [MODERN PAGES] Add web for adding CSS and Javascript on Sharepoint Modern Pages

    Add support for adding CSS and Javascript on Sharepoint Modern Pages.

    Here is an example implementation on github, but certainly my organisation will not implement it (straight out of github project), unless Microsoft can push this capability to Sharepoint:
    https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-script-editor

    Please see this image for more details, where I am trying to suggest adding a new Web Part for Scripts+CSS:
    https://i.imgur.com/dtpIzdY.png

    This capability is available in old Sharepoint Pages, so hopefully it should be easy to push in Modern Pages (which I really like to use).

    Regards

    49 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Site Scripts & Site Designs  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base