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. Provide a means to do audience filtering for list items over REST APIs

    List items that have an Audience field attached should be audience filtered when retrieved via the REST API.

    For example, a list that has link items with the Audience field attached to target particular items at particular groups of people. If the REST APIs are used to retrieve items from this list, then the identity of the requesting user should be optionally used to filter the results based on audience.

    119 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Fix the REST API to return the value and not the Id when getting single value Managed Metadata field

    REST API should be fixed when getting single value Managed Metadata since it returns the Id instead of the actual value, which then requires another call to get the value. Without this you cannot show a list of items/docs with the single Managed Metadata value. Note that "Allow Multiple" Managed Metadata works fine as it returns a collection of actual values.

    For details see: http://sharepointificate.blogspot.com/2014/05/taxonomy-columns-sharepoint-2013-list.html

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

    114 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Add the css for 'text-overflow' in Column Formatter.

    I want to truncate the string which crosses the width and add '...' at the end. Currently I am able to do that except for adding the '...'. It can be done if the column formatter supports 'text-overflow: ellipsis'.

    106 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. 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 →
  6. Add CSOM support for Document Set settings on content type

    Please consider adding support for setting/retrieving doucment set properties on a content type. We need to be able to set properties like Shared columns, Welcome page and Welcome page view on the document set.

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

    103 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 →
  8. 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,…

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

    96 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 →
  10. Fix CSOM SiteCollection Creation providing Lcid

    When creating Site Collections through CSOM and providing an LCID. (For example 2067) an exception is thrown.

    [Quote]
    SiteCreationProperties.Template\r\nParameter name: Specified value is not supported for the SiteCreationProperties.Template parameter." is thrown at ExecuteQuery();
    [/Quote]

    The Exception is also not pointing in the right direction.
    1) It should be possible to create Site Collections providing the LCID
    2) When an Invalid Lcid is passed, the exception should point in the right direction.

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

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

    92 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Add API that checks if user is in group

    Right now there is no API to check that. If you add a security group into a SharePoint group, there is no way to check if the current user is a part of the SharePoint group: The user is not listed in the group.Users and the SharePoint group is not listed in the user.Groups. The 3 APIs that allowed to do this in full trust code are missing from CSOM so we need an alternative.

    90 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. CSOM/REST - "open documents in the browser" (open in the client application, etc.) or allow "quick edit" (yes/now).

    Some list/library settings are available via CSOM. Others are available via the list property bag (although that approach is not desirable). However, there are even other advanced settings that don't appear to be accessible (read or write) via CSOM/REST. In particular, the advanced settings for "open documents in the browser" (open in the client application, etc.) or allow "quick edit" (yes/now).

    I'm looking at SharePoint 2013 when trying to do this, but I suspect the same problem occurs for SharePoint Online and SharePoint 2016.

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

  18. 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).

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

    71 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Site Scripts & Site Designs  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base