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 support for Single Page Applications to the SharePoint Framework

    As an example - Angular2 provides an excellent user experience, especially when tied to Bootstrap (v3 or v4) suitable for creating immersive experiences where the whole of the SharePoint chrome is replaced (other than the top bar).

    However integrating it with the SharePoint REST API framework is cumbersome and unless extensive work is undertaken to mock SharePoint the unit testing and rapid deployment is very unpleasant if possible at all.

    The SharePoint framework provides a rapid deployment and unit testable mechanism for developing SharePoint functionality but is limited to single web parts and extensions.

    Please extend the model so that…

    675 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    20 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add support for library packages in the SharePoint Framework

    When building web parts I'd like to be able to extract common code to a separate library that can be shared amongst the different web parts.

    Related issue on GitHub: https://github.com/SharePoint/sp-dev-docs/issues/467#issuecomment-284631927

    451 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! We’re happy to report that your suggestion was delivered as preview as part of the SharePoint Framework 1.8 release. See more details from the release notes – https://github.com/SharePoint/sp-dev-docs/wiki/SharePoint-Framework-v1.8-release-notes and from the official SharePoint dev documentation at http://aka.ms/spdev-docs. This capability is currently in preview, but will be shipping close as is to production soon, so we are closing this already to ensure that the progress is noted.

  3. Provide items version history with CSOM

    Provide the Version History feature on list items with CSOM, i.e. provide which metadata has changed with the previous value.
    Currently, the only way to retrieve versions is through the FileVersionCollection/FileVersion objects which provides only the VersionLabel, CreatedBy, CreationDate and Version Url.

    Ideally, we would need a ListItem object holding all the attributes and values for each version - or at least the attributes that have changed.

    415 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Ability to use App-Only calls to create modern sites

    Provide support to create modern sites using App-Only calls.

    382 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. UserProfile.Manipulation.CSOM is needed on premises

    Now we can update UP properties via CSOM in O365, but not on premises. I would appreciate if this can be included on-prem, my customers 80% of the time are still on-prem

    304 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    We don’t really have a good status for this one, so using the most accurate one. CSOM based manipulation for user profile properties IS available in on-premises in SP2016 and in upcoming SP2019 versions. This is not, however, something which will be backported to the SP2013 platform, meaning that this capability will NOT be available from the SP2013 platform.

    In SP2016 and in upcoming SP2019, you can use public method Microsoft.SharePoint.Client.UserProfiles.PeopleManager.SetSingleValueProfileProperty and public method Microsoft.SharePoint.Client.UserProfiles.PeopleManager.SetMultiValuedProfileProperty to manipulate user profile property values for a specific user profile.

    Thank you very much for your input on this capability.

  6. Enable support for lookup columns in other webs in the REST API

    When trying to retreive items from a list which uses a Site Column that is a looukp column to a list in a different web, we get the error:

    {error":{"code":"-1, Microsoft.SharePoint.SPException","message":{"lang":"en-US","value":"The field 'TrouserSize' is not supported in query. The lookup list is in another web."}}}

    297 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback! We’re happy to report that your suggestion is now part of the RenderListDataAsStream method in the list REST APIs. You can find updated documentation on the RenderListDataAsStream operation from SharePoint Dev documentation at https://docs.microsoft.com/en-us/sharepoint/dev/sp-add-ins/working-with-lists-and-list-items-with-rest#working-with-list-items-by-using-rest.

    This is the same method which is used by 1st party functionalities to resolve complex fields such as lookups and managed metadata fields.

  7. Adding Apps from Catalog or Store using CSOM API

    As provisioning process, we would love to either add apps from app catalog or store directly using CSOM APIs. This should include the 'I Trust it' model as well. This will help in automating the entire site/sub-site provisioning and making sure apps are available after site is created.

    259 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Make it easier to develop javascript based web parts

    Provide a better story than App Parts or Script Editors for custom web part development. I'd like to see a javascript based web part framework that would allow developers to build in their own "Editor Parts" using javascript and allow for serialization of web part properties (perhaps stored as JSON string).

    Too much overhead with App Parts, and also they require iframe usage. Script Editors are a bit "wild west" and don't provide structure for editing custom properties.

    234 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback! We’re happy to report that your suggestion is considered to be delivered with the SharePoint Framework GA and subsequent releases since February 2017. SharePoint Framework is designed to address this request and to provide a standardized framework for the JavaScript customizations with client-side web parts and newly released SharePoint Framework Extensions. Please check more details on the SharePoint Framework from http://aka.ms/spfx.

    We consider this wider topic now to be delivered, but absolutely understand that there are numerous small sub-requests around the improvements for JavaScript development. We would suggest requesting those in more specific submissions so that we can more easily prioritize and deliver them gradually.

    We are also more than interested in your feedback around the SharePoint Framework. Please use following resources to start a discussion with our team. Thank you for your valuable input advance.

    - sp-dev-docs repository issue list – https://github.com/SharePoint/sp-dev-docs/issues)
    -…

  9. Add ability to download old version of a file via API/CSOM

    One should be able to download an older version of a file using something like:
    FileInformation info = File.OpenBinaryDirect(context, "/" + _fileVersion.Url);

    But instead that throws a 401 error.

    See MSDN thread here: http://social.msdn.microsoft.com/Forums/en-US/7746d857-d351-49cc-b2f0-496663239e02/how-to-download-a-file-version-from-office-365-using-csom?forum=sharepointdevelopment

    229 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback! We’re happy to report that your suggestion is now part of the September 2017 version of the CSOM NuGet package. You can find details and simple code sample from following blog post – https://dev.office.com/blogs/new-sharepoint-csom-version-released-for-Office-365-september-2017.

    Technically file access has been available for a while with SharePoint Online CSOM, but with the latest updates, you can also access list item field version and we have included a code sample for the APIs in this blog post also around file version downloading.

  10. Provide clear support statement for SPFx with IE

    Right now there is no clear statement regarding the supportability of IE with SPFx. Since IE 11 is still supported for O365 and SharePoint Online, customers assume that it is supported with IE as well.
    Currently SPFx is impossible to use with IE because of performance issues and very bad memory leaks in IE. The more content and web parts are on a modern page the worse it gets. Thus, I suggest that you either fix those issues, or make a clear statement that SPFx is not supported with IE anymore. This would really help customers in making their decisions.

    180 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 →

    We have now provided explicitly supportability statement for the IE 11 in the context of SharePoint Online at following location: https://support.office.com/en-us/article/which-browsers-work-with-office-for-the-web-ad1303e0-a318-47aa-b409-d3a5eb44e452?ui=en-US&rs=en-US&ad=US

    “Modern pages, lists and libraries on SharePoint Online are only supported in Internet Explorer 11 when Document mode is set to Internet Explorer 11”

    Other browser modes are unfortunately not using modern web technologies and are not supported as such.

    If you find any issues on the SharePoint Framework capabilities with IE 11 which is in the IE 11 mode, please open an issue at http://aka.ms/spdev-issues with sufficient details, so that we can provide support for your issue.

    Hopefully that provides the needed clarity on the situation.

  11. SPListItem.SystemUpdate(boolean incrementListItemVersion) in CSOM

    I have not been able to find an equivalent function in CSOM to update a list item without affecting the Modified or Modified By fields. Please add this functionality to CSOM SP2013.

    122 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We are happy to provide this update as part of the SPO CSOM updates released late August 2016. See more details from following blog post – dev.office.com/blogs/new-sharepoint-csom-version-released-for-Office-365-august-2016-updated.

    Thanks for providing your valuable input on the needed APIs and product capabilities.

  12. Add support to the ReadSecurity and WriteSecurity list properties from the CSOM.

    CSOM does not allow view/edit of the properties in reference: http://msdn.microsoft.com/en-us/library/office/dn531433(v=office.15).aspx#bk_ListProperties

    For example, the code below fails:

    $.ajax({
    url: "/_api/Web/Lists/GetByTitle('Documents')/ReadSecurity",
    type: "GET", dataType: "json", headers: { Accept: "application/json;odata=verbose"}
    }).done(function (data){ console.log(data.d.ReadSecurity);})
    .fail(function(e) { console.log(e.statusText);});

    119 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We are happy to provide this update as part of the SPO CSOM updates released late August 2016. See more details from following blog post – dev.office.com/blogs/new-sharepoint-csom-version-released-for-Office-365-august-2016-updated.

    Thanks for providing your valuable input on the needed APIs and product capabilities.

  13. Enable ListItem SystemUpdate via CSOM

    SystemUpdate for List Item is not supported in CSOM today. If we update the metadata, it creates a new version and triggers workflows. We have to use Server Side Object Model via OnPremise SharePoint or Sandbox solutions for one of our scenarios requiring SystemUpdate.
    Adding support, say for Site Collection Admin accounts only, will bring CSOM closer to being on part with Server Side Object Model.

    102 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We are happy to provide this update as part of the SPO CSOM updates released late August 2016. See more details from following blog post – dev.office.com/blogs/new-sharepoint-csom-version-released-for-Office-365-august-2016-updated.

    Thanks for providing your valuable input on the needed APIs and product capabilities.

  14. Remove pop-up requirement for Graph API SPFx web parts

    Graph API web parts have a huge amount of potential for SPFx web parts and extensions. The preview version requires pop-ups which are not user friendly. In some environments pop-ups will be blocked by group policy. This is a ADAL.JS dependency but moving forwards it would be a backwards step to require pop-ups and make SharePoint less user friendly again. Vote for this and lets make MS move this forwards in the right direction.

    94 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 →

    We are happy to update you on significant changes with this capability as part of the SharePoint Framework 1.6 release, which technically removes the requirement of the popup.

    As this capability is using adal.js under the hood (only GA capability in JS for Azure AD), there are still some edge scenarios where the popup might happen, so solution is not quite perfect due to the limitations in the AAD side, but it’s the best possible implementation and in normal scenarios you will not see any popups when accessing Graph information.

  15. Add additional permissions to GraphHttpClient

    With the graph GQL gone, having this "easy" method to query Graph API directly from SharePoint when already authenticated is a huge must have.

    For example I'd ask priority on the permissions that let you fetch Recent Files, Trending Files, Trending People, and Planner tasks for the current user. Those make the most sense to be featured on intranet home pages. We do this currently (and it is quite messy with adal.js, particular when it comes to token refreshes), but has lots of end user value.

    I have 4 custom web parts today in a SEWP. One gets recent documents,…

    81 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! We’re happy to report that your suggestion is now part of the SPFx v1.4.1 release with the introduction of AadHttpClient and MSGraphClient classes, which will replace the previously available GraphHttpClient. This new capability is now in preview, in similar ways as GraphHttpClient was, but is planned to move to General Availability within spring 2018. You can read more details on the possibility to use ANY Graph scope from https://docs.microsoft.com/en-us/sharepoint/dev/spfx/use-msgraph.

  16. Enhance FieldLink class with additional properties - DisplayName, ReadOnly, ShowInDisplayForm

    Microsoft.SharePoint.Client class misses DisplayName, ReadOnly, ShowInDisplayForm properties.

    Most important of the first one - DisplayName.
    Missing that property leads us to create new field to every single content type as we cannot rename the field which is added to the content type.

    75 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We are happy to provide this update as part of the SPO CSOM updates released late August 2016. See more details from following blog post – dev.office.com/blogs/new-sharepoint-csom-version-released-for-Office-365-august-2016-updated.

    Thanks for providing your valuable input on the needed APIs and product capabilities.

  17. Add full API for alerts

    Add full API for alerts so you can create, edit and delete alerts for any user through CSOM/REST

    72 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Implement REST\CSOM API method for setting list read and write security

    Implement SPList.ReadSecurity and SPList.WriteSecurity for client model, like in the server object model.

    70 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We are happy to provide this update as part of the SPO CSOM updates released late August 2016. See more details from following blog post – dev.office.com/blogs/new-sharepoint-csom-version-released-for-Office-365-august-2016-updated.

    Thanks for providing your valuable input on the needed APIs and product capabilities.

  19. Make it possible to use SharePoint Search with app-only context

    Currently it is only possible to execute search queries with user context. Allowing for using SharePoint Search with app-only context would make it possible to make better use of the platform and build richer solutions and apps.

    63 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. EnableAssignToEmail List method missing on List object in CSOM

    Hi,

    We've run across a gap in our implementation of the Remote Provisioning model for new Site Collections - the EnableAssignToEmail property on the CSOM List object does not exist. There is no way we can see to automate this setting as part of site creation.

    This property corresponds to the Send e-mail when ownership is assigned? setting on certain list types.

    60 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We are happy to provide this update as part of the SPO CSOM updates released late August 2016. See more details from following blog post – dev.office.com/blogs/new-sharepoint-csom-version-released-for-Office-365-august-2016-updated.

    Thanks for providing your valuable input on the needed APIs and product capabilities.

← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base