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. Support OData $inlinecount operator in REST API

    The OData v3 specification (which I believe the SharePoint REST API is supposed to be v3) supports an operator to include the total row count for a query in the response. The Project Online /api/ProjectData endpoint supports it as well. However it seems the /api/Lists endpoint does not for some reason.

    Could you "fix" this so the Lists API is OData compliant?

    See section 10.2.3.6 here: http://www.odata.org/documentation/odata-version-3-0/odata-version-3-0-core-protocol/

    3 votes
    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 APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add build parameters for overriding default config.json and package-solution.json locations

    Currently SPFx build process assumes that project only has one config.json and one package-solution.json file. For projects that are deployed to multiple tenants this limitation should be removed.

    Easiest way would be to add some build parameters that can be used to override locations of those files. e.g.
    gulp package-solution --ship -solutionfile mycustomfolder/package-client1.json

    3 votes
    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 →
  3. Remove the 5000 View Threshold for REST API or CSOM

    There is no need to limit View Threshold when querying against REST or CSOM. Remove the Threshold in order to pull large data.

    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 APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support changing Calendar view Overlay using APIs

    Right now in the SharePoint Online Client APIs (Whether it is CSOM or REST) we can't change the CalendarSettings properties to override the current Overlay Calendar of a View.

    It used to be doable in SharePoint 2010/2013, but on SharePoint Online CSOM there is no CalendarSettings member of the View.

    The closest we can get it the HtmlSchemaXml which includes the AggregationCalendars node but it's read only.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Possible to Add Labels to Documents Librarys from CSOM/REST/JSOM

    Possible to add/remove/list Labels to document Library , via REST/CSOM/JSOM

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. 4 votes
    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 →
  7. Browsing the apps under From Your Organization

    Under apps From Your Organization, we can not distinguish apps from
    Site Collection App Catalog and apps fromTenant App Catalog.

    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 →
  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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  9. Write to Web Property Bags

    The ability to both read and write to the various property bags would be very helpful. Currently it's possible to read from a web property bag, but not to write. It'd be even better if the other property bags supported this.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Make SPFx projects compatible with TSLint VSCode extension

    Make SPFx projects compatible with TSLint VSCode extension by either moving the tslint.json file to the root folder or by creating a new tslint.json at the root that instructs the VSCode extension to look for rules on the config folder

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
  11. SharePoint Extensions on Classic Sites

    Please, make it possible to use SharePoint Extensions on Classic sites in order to use common components throughout the tenant. A good example is the Footer, we want to use the same footer so we don't have to build two different components in two different technologies.

    2 votes
    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 →
  12. publishing Image column

    Support for PublishingPageImage & PubliblishingPageIcon in REST API. Now we need two API requests to get the columns.

    3 votes
    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 APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →
  13. Fix the issue regarding sharepoint list column name

    Sharepoint will not be able to issue the xml list of lists when one of the column is named with symbols only such as "***" or "-" . If this is causing issues they should either be resolved or the column should not permit being named in this way.

    thanks

    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 →
  14. Create Retention polices /Labels with REST API

    Create Retention polices /Labels with REST API

    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 APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →
  15. JSOM/CSOM Threshold issue

    Please enable support for CSOM/JSOM/REST query to process request for large list rather than hitting into threshold issue. Even the column is indexed and you query based on the indexed column, threshold error is returned.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. 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

    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 →
  17. Provide client side API to manipulate ContentType XmlDocuments

    As far as I know, there's no way to manipulate XmlDocuments collection of ContentType objects.

    On server side, we can directly use SPContentType.XmlDocuments to manipulate the collection, but I didn't find any client side way to do this.

    Neither CSOM, nor REST API nor Web service provide something able to reach my goal.

    XmlDocuments collection is useful to store content type related configuration. There is OOB configuration like policies, or receivers stored in this collection, and some 3rd party data too (at least we are trying to).

    Thanks

    3 votes
    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 APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →
  18. SPFX > Use query builder in Propertypane

    I would like to use the SharePoint Query builder. As we are used to have in the Web-part properties (like the CEWP).
    In SPFX I would like to use it in the Propertypane of a SPFX webpart.

    3 votes
    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 →
  19. Workflow using REST on an indexed lookup to another list in the same web fails with a generic error when the active list is over 5k items

    Workflow using REST on an indexed lookup to another list in the same web fails with a generic error when the active list is over 5k items. Works fine if under 5k items in the source list. This is contrary to the documentation on using rest - either update the documentation or fix this issue.

    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 APIs (CSOM/REST/Server-side)  ·  Flag idea as inappropriate…  ·  Admin →
  20. SharePoint 2016 Shared With Popup URL redirection issue

    SharePoint 2016 Default redirection having an issue.

    Issue Explained in below URL. Please check.
    https://social.technet.microsoft.com/Forums/en-US/792f5c20-5708-4176-b658-6786fe0b24af/sharepoint-2016-shared-with-popup-url-redirection-issue?forum=sharepointdevelopment

    Resolution:
    After clicking the close button in view documents properties page directly redirect to document library rather then back (popup page).

    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 →
  • Don't see your idea?

Feedback and Knowledge Base