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.

Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more

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. Make the name of the current Composed Look a property of the Web object

    Currently there is no simple way to pro grammatically get/set the current Composed Look for a site. The Composed Looks list available from the Site Settings page shows all the looks available, but the only way to determine which one of them is the current one is to tediously compare every item in the list to the one with the name "current", which is inefficient and error prone because if there is a background image as part of the Composed Look, the value in the background image field is changed when the look is chosen by the user so the…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now. This would absolutely help on the programmatic handling of the site configuration, but we are not currently looking to invest in this area of the branding elements.

  2. ItemModertorStatusChanged event receiver

    ItemUpdated event receiver is a very rough async process that blocks SharePoint functionality heavily. It can't be empty since workflows communicate with SharePoint using it. My Suggestion is to introduce a ItemModertorStatusChanged event receiver. To obtain backwards comptibility, it should be a tick box when creating a workflow in SharePoint Designer to use ItemUpdated or ItemModertorStatusChanged event receiver.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now. Your suggestion does make sense but would require changes across multiple areas, where we are not currently planning to invest.

  3. Need a telephone number to learn how to repair smoke alarm

    Need telephone number to Kidde for troubleshooting smoke alarm.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  4. A30357714

    A30357714

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Add-ins  ·  Flag idea as inappropriate…  ·  Admin →
  5. NAPA supporting ECMAScript 2015 or Typescript for both on- and off-premise programming of event receivers

    Present programming of Remote Event Receivers is complicated and limited so farm deployed server-side Event receivers are used. Support of ECMAScript 2015 or Typescript is needed in a simple freestanding tool (NAPA?) for both on- and off-premise installations.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now. NAPA service is no longer supported and the models are moving more towards scenarios with web hooks and Azure functions.

  6. Worklflow 2013 should have MORE functionality than WF 2010

    8pproval Workflow functionality is limited. A ItemModertorStusChanged event reciver is missing. WF 2010 has more functionality and hence used instead of WF2013. Even with WF2010 it is tricky to get appovers names and dates into library columns. SharePoint Designer 2013 is unstable and may corrupt the system!

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now. In SharePoint Online we are gradually moving towards Flow from the classic workflow scenarios. In on-premises workflow is absolutely supported and there should not be any corrupt issues. If that would be the case, it would be rather a bug than a new feature. We do understand the importance of the business processes support and are looking to further invest in this area also in future, but not using the classic concepts.

  7. Foooooooopoooooooooole bot

    Project bizines teknolezhi and abar clencher and abar news
    a ND وقطب بزرگ اطلاعات از تمام شاخه ها و رشته ها

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now through SP dev team. This falls more on the Windows server side enhancements and our team cannot, unfortunately, act on this as such. We do though appreciate your input and agree that TMG was a great product for a purpose in on-premise.

  9. Combining different extension Types

    Right now SharePoint Framework Extensions support three different types of extensions: ApplicationCustomizers, FieldCustomizers and CommandSets . Can we combine two extensions under one project. Example: Based on selected List items in the list, do some customization in the header bar using Application Customizer. Please suggest.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    This is absolutely supported and you can have as many extensions or web parts in single solution talking between each other. There are numerous options for the components to communicate with each other. One of such options is demonstrated in following sample in SharePoint GitHub – https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-rxjs-event-emitter. Since this is not really a new feature request, we will close the issue. Would suggest having questions and discussions in StackExchange, GitHub or in SP Tech Community.

  10. Cannot resolve schema file path in manifest.json using SPFx.

    When I create a new SPFx webpart, "$schema" path is wrong in WebPart.manifest.json. It must be "client-side-component-manifest.schema.json", but current is "clientSideComponentManifestSchema.json".

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    Thx for submitting this. This is clearly a bug and should have been already addressed with the v1.2 release. In future, if you have seen any specific bugs or random issues, we would recommend using https://github.com/SharePoint/sp-dev-docs/issues issue list to start a discussion with SharePoint engineering. Uservoice is mainly for the new feature requests and possible issues can, unfortunately, get hidden here. Thx anyway for the submission and please let us know in the issue list if you still have any questions.

  11. List-Library Settings Access via CSOM

    Provide extra capabilities to deal with SharePoint List settings using CSOM.

    Currently some of the properties of List are not accessible using CSOM.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, we need to have more specific requests around what’s needed. We would appreciate more specific properties which you need so that we can evaluate exposure of them one-by-one. Thx.

1 2 3 5 Next →
  • Don't see your idea?

Feedback and Knowledge Base