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

    15 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. SPFX ListViewCommandSet > use Fabric UI ICON

    Within the SPFX 'extension' framework, there's no way to specify an icon for a ribbon button - list view extender.

    This blog post mentions it - but no resolution ;
    https://github.com/SharePoint/sp-dev-docs/issues/642

    Ideally, there would be a property for ; officeFabricIconFontName

    14 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 →
  3. Set Default Column Values using a Site Script Verb (Site Design)

    I am a fan of Site Designs; however, I would like to be able to set Default Column Values on lists and folders.

    You could complete this action using the UI or the Set-PnPDefaultColumnValues PowerShell complete. Sadly, this is not in acceptable to the average “business user” and required administrator input.

    Please add a verb called setDefaultColumnValues to SharePoint Site Scripts?

    14 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 →
  4. Fix search wildcard issue or provide more useful message

    We have found an issue with property queries using REST that also occurs when using the SharePoint UI via a browser. Using the following query results in an error in the browser and also when executing the query via the REST API:

    Title:"Jan de*"

    I seems that any property query on Title that contains more than one word and where the last word has a wildcard at the end results in this error:

    Search has encountered a problem that prevents results from being returned. If the issue persists, please contact your administrator.

    Correlation ID...

    The following variations all work fine:

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. AAD app-only access site permission control

    As described in this doc: https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/security-apponly-azuread
    When granted All Site Full Control permission, the application would be able to access all sites in my organization. But can we grant permissions to specific sites? In other words, can we restrict the sites the application can access? If we can, how to do this?

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. BUG: Online workbench doesn't reflect the theme colors of the parent web properly

    There is a bug in the Online Workbench that you are not able to test theming on your web parts when the following two themes will be used:
    * Dark Yellow
    * Dark Blue

    As documented in the Issue on GitHub https://github.com/SharePoint/sp-dev-docs/issues/1064

    This would be really beneficial for testing web parts and how they look like when different themes will be used.

    13 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. Linked to item lookup column (from a different list) pops up dialog box - but JSON button/icon/href display doesn't open dialog box

    I created a column that is a linked to item lookup field to a different list and pops up a dialog box to that item when clicked. I only get @currentField.lookupId or @currentField.lookupValue for the JSON formatting - and would like to have the "@currentField.lookupUrl" so that I can display a button or different link text - yet have it act like the "linked to item" link which inherits whether or not it opens in a dialog box from the "advanced settings" or the list.

    13 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 →
  8. JSON formatting: Add .parse() and .split() operands

    JSON formatting is nice and dandy, I would like some more operators though.

    Specifically .parse() to interpret the contents of @currentField as a JSON object, and split() to interpret is an an array, split by whichever operator is provided.

    13 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 →
  9. pageContext.web.description and pageContext.user.id

    Web description and user id are both strangely missing from the page context. It would be great of they were available.

    13 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 →
  10. Ability to hide column on content type

    Add the ability to hide column when adding it to the content type - on the addSiteColumn JSON script.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Site Scripts & Site Designs  ·  Flag idea as inappropriate…  ·  Admin →
  11. Add UseAccessRequestDefault Rest API or CSOM when receiver is the team site owner in Access Request Settings.

    Environment: SPO

    There is a new option to allow the team site owners to receive the access requests email, but there is no Rest API/CSOM to support this, Please have add this into CSOM API, Thank you.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Enable to add web parts programmatically to newly created modern sites

    Currently, it's not possible to add a web part to a newly created modern site (communication or team site):


    • Adding a web part is not supported in site designs.

    • Adding a web part with PnP (CSOM: ClientSidePage.AddControl; PowerShell: Add-PnPClientSideWebPart) removes all default web parts.

    It would be good to support either scenario or, even better, both.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Site Scripts & Site Designs  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow clientId instead of resourceName when requesting webApiPermissions

    When using the SharePoint Framework, you should be able to request webApiPermissions via the resource client Id OR the resource name.

    We have a multi-tenant application that's deployed to a couple dozen tenancies that we would like to rename. However, since permissions are requested by name, any attempt to rename the application may be met with our users having to go through the install process again. Being able to instead request access via the clientId would allow us to safely rename without having to worry about our users losing access.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint Add-ins  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add Records.BypassLocks to the Client APIs

    CSOM contains very few methods compared to the Server Object Model equivalent relating to records management.

    There are only three methods; DeclareAsRecord, IsRecord and UndeclareAsRecord available to clients, compared to 25 methods in the Server Object Model.

    Many records management solutions for SharePoint that exist today as Full-Trust solutions make use of methods that are not included in CSOM, but a large number of these can be worked around with existing CSOM (for example, finding the declaration date of a record).

    One very important method that is missing however is Records.BypassLocks.

    This method is used to support a variety of…

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. EndPoint RenderListDataAsStream full compatibility with Task List (template 171)

    If a Task list (template 171) has fewer than 5000 items, the performance of the RenderListDataAsStream endpoint is inappropriate (try with 4999 items). If the list has 5000 or more elements the performance becomes excellent. I know that the tasks lists are not compatible with Modern UI, but this should not affect the RenderListDataAsStream endpoint as well.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Provide CSOM API for Enabling/Disabling the option "Allow items in this list to be edited using Quick Edit and the Details Pane"

    Provide CSOM API for Enabling/Disabling the option "Allow items in this list to be edited using Quick Edit and the Details Pane".

    After migration of SharePoint Previous versions to SharePoint online, there are instances where the quick edit or edits from details pane needs to be disabled, for lists across thousands of site collections. This is very challenging task if has to be done manually for huge scale of site collections.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. JSON Formatting: regional settings with date

    When using @now to format views/columns using JSON the date is taken as the US style (mm/dd/yyyy) regardless of the regional settings of the tenant. It would be useful if it either uses the date format of the tenant, or allows the user to specify the date format. For more details of the problem see here: https://social.technet.microsoft.com/Forums/msonline/en-US/21712788-fafa-4898-9cee-897d1b3afb88/modern-list-view-formatting-with-uk-dates?forum=onlineservicessharepoint

    11 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 →
  18. Create roledefinitions and groups from SiteDesign

    Please add functionality to create roledefinitions, create custom groups and assign roledefinitions to groups.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Site Scripts & Site Designs  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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 →
  20. Provide method for extending out of box SPFX web Parts

    Much like the classic SSOM model of extending OOB web parts, provide a way (or open source them ;-)) the SPFX web parts to allow Devs to build upon what you have already built.

    Its a bit old school, but has value in providing Devs a way to extend existing web parts leverage them and tweak them according to specific requirements. Perhaps with a change caveat that if you change it does not update our custom ones based upon it.

    10 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 →
1 2 5 7 9 19 20
  • Don't see your idea?

Feedback and Knowledge Base