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 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…)
  2. 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…)
  3. 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.

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

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

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

  8. CSOM .NET async support

    CSOM for both Silverlight and JavaScript have an ExecuteQueryAsync method. This is not available for the .NET version.

    Currently, ExecuteQuery blocks the current thread and in the context of an ASP.Net application this is very resource intensive - the request thread cannot be used to service other threads whilst ExecuteQuery is waiting for a response.

    ASP.Net applications only have a small number of threads proportionate to the number of cores and the lack of async support makes it very difficult to write SharePoint provider-hosted add-ins capable of handling large numbers of concurrent requests.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Support ComplianceTag on the CSOM list object

    Today CSOM expose ComplianceTag per item in a list/library. The library UI support setting a default ComplianceTag. Having this property in CSOM would be useful for provisioning scenarios.

    If you look at the SchemaXml for the list the property is visible.

    13 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 SPO CSOM package. Please do submit an additional item for any other requests, like on having this on the content type level, as we cannot track additional requests simply on the UserVoice comments. Thx.

  10. Extend SharePoint REST API to retrieve list by staticname

    We have a solution which provisions lists to several site collections. There can be different language version, so list display names are localized. It would be nice have a REST endpoint to retrieve list by it's internal name.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  • Don't see your idea?

Feedback and Knowledge Base