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
- Check if it's already been suggested. If it has, vote for it.
- If it's new, submit it in 50 words or less.
- Gather support!
- 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.
-
Allow us to develop custom modern forms with custom edit experience
We would like to be able to create an SPFx form and associate it with the List/Content type Disp, Edit, New form so that no matter how a user finds a list item (search, OOB list view, custom list view, etc) they see our custom form. Currently our only option is to create a completely disconnected experience in which we write a custom list view that points to custom form pages.
Alternatively support field customizers with edit model to enable custom field editing experience.
2,364 votesThanks for your feedback! We’re reviewing your suggestion.
-
When creating an SPFx Extension for a custom header, provide a configurable property that allows the composite header to be hidden
When developing a SharePoint Framework Extension to display a custom header and/or footer, the SharePoint Composite Header can be very redundant to the custom header.
The Composite Header (css classname is 'ms-compositeHeader'), is what SharePoint provide out of the box and includes the square site logo, site name and navigation.
When creating your own custom header that includes all of these things and possibly more, the existence of the Composite Header is redundant and can be confusing for users...(Ex: redundant navigation).
While CSS can be used to hide this, such a technique is not playing within the rules of only…
739 votesThanks for your feedback! We’re reviewing your suggestion.
-
Support SharePoint 2016/2019 with .NET Standard APIs
While the SharePoint online version is supported, we would like to see the SharePoint on-prem versions (SharePoint 2016/2019) supported with .NET standard CSOM APIs.
https://sharepoint.uservoice.com/forums/329220-sharepoint-dev-platform/suggestions/16585795-support-net-core-with-csom
^ this only allows for SharePoint Online .NET Standard CSOM support.Many customers have significant investments and longer term roadmaps to get to SharePoint Online, but in the interim would like to start developing solutions that can be more easily converted to work in SharePoint Online along with being able to leverage the latest version of the Microsoft technology stack - that is growing the skillsets / toolset familiarity without waiting for longer term plans…
396 votesThanks for your feedback! We’re reviewing your suggestion. We are hoping that we can provide some positive news on this sooner or later. Thank you for providing the input around this specific request.
-
Allow to use Office UI Fabric Icons and other fonts as Command Set icons
It would be great if we are able to use font icons instead of url to images for Command Set extensions buttons icons.
This allow 3d party extensions look more aligned with 1st party (same style, same icon color)366 votesThanks for your feedback! We’re reviewing your suggestion.
-
Extensions: Property Pane / SideBar Placeholder (Right)
Please provide a well-known placeholder for the property pane or better a similar placeholder that let us create a sidebar.
Having this ability would let us create powerful sidebars/toolbox extensions. This would be a super cool enhancement!
221 votesThanks for your feedback! We’re reviewing your suggestion.
-
Line up list item pagination with REST API using $top and $skip
Actually, the only way to paginate list items using the new REST APIs is to use __next property. There's no way to have a full working pagination using $top and $skip token as for any other REST call.
See my comment here:
http://msdn.microsoft.com/library/d4b5c277-ed50-420c-8a9b-860342284b72.aspx202 votesThanks for your feedback! We’re reviewing your suggestion.
-
Provide flag to enable\disable event firing from Remote Event Receivers
Provide option to enable\disable event firing from Remote Event Receivers in SharePoint Online (CSOM/API) similar to SSOM - EventFiringEnabled
199 votesThanks for your feedback! We’re reviewing your suggestion. This could be also useful for new WebHooks, so still relevant.
-
SPFx Key/Value Pair Properties that support Read/Write
Provide a SharePoint Framework mechanism/API that allows for Site or Site Collection Read/Write of Key/Value pair properties for use in SPFx related configuration and customizations. Similar to how the property bag was used in classic.
One use case is for storing configurable properties or even user personalization configurations written and read by an SPFx solution.
This is one of many uses cases that would make this feature valuable, so in addition to your vote, please feel free to comment with additional ways in which this feature could provide additional value.
194 votes -
API for "Create Team from Template" with Site Design
We can do templating on SharePoint, through Site Designs and Site Scripts. We now also have the option to "Create a Microsoft Teams from Template".
Unfortunately, both do not work together. We either have a templated SharePoint site with a generic Teams or a templated Teams with generic SharePoint site.I would love the possibility to combine both templating options. Preferrably with an API from day 1.
This would give us an end to end templating scenario, where we can create preconfigured Teams with a preconfigured SharePoint site. (In the future, hopefully with a preconfigured Planner etc as well ;)…194 votesThanks for your feedback! We’re reviewing your suggestion.
-
Improved API feedback around throttling
Currently working with the API's for drive, graph, sharepoint are very difficult due to the throttling that can be encountered.
Each api offers different guidance to avoid throttling. Example are:
1) use a special user-agent header
2) respect the retry-after headerSpeaking with microsoft representatives they instruct us to perform major api processing in off peak hours. Additionally tenant's can have hard locks placed on them.
This request is to get better information around tenant usage returned in the API's.
1) If a tenant is hard locked, tell us in a distinct message so that don't just hammer the requests…
176 votesThanks for your feedback! We’re reviewing your suggestion.
-
Allow extending SharePoint Admin Center using SPFx
It would be nice to have the ability to extend some of the functionality in the SharePoint Admin Center. Specifically, the ability to deploy SharePoint Framework Web Parts into the Admin Center (via an App Page?). Currently, the community builds lots of SPFx Web Parts to fill the gaps in the Modern UX.
Such Web Parts include:
Theme Manager
Site Design Studio/ManagerThese are SPFx solutions that have been built to help better manage our environments through a UX experience (as there isn't one via First Party). It would be nice to have a centralized location where these SPFx solutions…
178 votesThanks for your feedback! We’re reviewing your suggestion.
-
Enterprise Deployment of SharePoint Framework Apps in an On Premise Platform
There is currently no good way to do enterprise level automated deployments of an SPFX addin into a SharePoint 2016 on Premise environment..
Consider a case where there are 1000 site collections and we would need to deploy an SPFX app to all sites automatically. Currently there is no way to perform this deployment in an automated fashion. It is not possible through powershell, csom, c# or in an administrative UI.
Having this ability would solve a large hole in capabilities with SharePoint Framework
148 votesThanks for your feedback! We’re reviewing your suggestion.
-
Provide a means to do audience filtering for list items over REST APIs
List items that have an Audience field attached should be audience filtered when retrieved via the REST API.
For example, a list that has link items with the Audience field attached to target particular items at particular groups of people. If the REST APIs are used to retrieve items from this list, then the identity of the requesting user should be optionally used to filter the results based on audience.
139 votesThanks for your feedback! We’re reviewing your suggestion.
-
Extensions: Application Customizer get page all components data (List, Documents, Search etc..)
Provide a way to get data about all components that present on page in ApplicationCustomizer like SearchBox, Search, Documents Library, Lists, Navigation bar etc.
The idea is to have full control on user interaction with components.
In example I want to make an additional action when user clicks on folder, file, list item, navigation item, search result item etc...
Ideally to have access to domElement and data model of component.
107 votesThanks for your feedback! We’re reviewing your suggestion.
-
Add API that checks if user is in group
Right now there is no API to check that. If you add a security group into a SharePoint group, there is no way to check if the current user is a part of the SharePoint group: The user is not listed in the group.Users and the SharePoint group is not listed in the user.Groups. The 3 APIs that allowed to do this in full trust code are missing from CSOM so we need an alternative.
102 votesThanks for your feedback! We’re reviewing your suggestion.
-
Content type remote event receivers
Remote event receivers can currently, in SharePoint Online, not be added to content types (https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.client.contenttype_members.aspx). This makes it somehow tedious to catch events that are fired from items of a specific content type is added/updated/deleted. Having the possibility to add an event receiver to a content type would make this scenario easier to implement.
100 votesThanks for your feedback! We’re reviewing your suggestion.
-
Fix CSOM SiteCollection Creation providing Lcid
When creating Site Collections through CSOM and providing an LCID. (For example 2067) an exception is thrown.
[Quote]
SiteCreationProperties.Template\r\nParameter name: Specified value is not supported for the SiteCreationProperties.Template parameter." is thrown at ExecuteQuery();
[/Quote]The Exception is also not pointing in the right direction.
1) It should be possible to create Site Collections providing the LCID
2) When an Invalid Lcid is passed, the exception should point in the right direction.93 votesThanks for your feedback! We’re reviewing your suggestion.
-
CSOM/REST - "open documents in the browser" (open in the client application, etc.) or allow "quick edit" (yes/now).
Some list/library settings are available via CSOM. Others are available via the list property bag (although that approach is not desirable). However, there are even other advanced settings that don't appear to be accessible (read or write) via CSOM/REST. In particular, the advanced settings for "open documents in the browser" (open in the client application, etc.) or allow "quick edit" (yes/now).
I'm looking at SharePoint 2013 when trying to do this, but I suspect the same problem occurs for SharePoint Online and SharePoint 2016.
86 votesThanks for your feedback! We’re reviewing your suggestion.
-
Allow calling an HTTP-triggered Flow after installing SPFx solution in a site
When creating sites using a site design (recipe), one of the available verbs is calling an HTTP-triggered Flow to perform some additional configuration on the newly created site.
When installing SPFx solutions in a site, we should similarly be able to specify an HTTP-triggered Flow to be called as a part of the installation process. This would not only allow developers to provision configuration beyond what's currently supported with Feature XML, but also create a consistent development experience across the different workloads (site designs vs. SPFx).
82 votesThanks for your feedback! We’re reviewing your suggestion.
-
Add User Profile changes functionality to CSOM/REST
When switching the development model from SharePoint server OM to SharePoint Apps (CSOM), there is one important feature that we are missing: the User Profile Changes API (http://msdn.microsoft.com/en-us/library/office/ms517376(v=office.14).aspx ).
In an on premise environment there is still a way to implement this using server OM but in cloud environments there is no way to do it.
Apparently the only way of synchronizing SharePoint user profiles or handle user profile changes in the App model is doing a brute-force full scan using CSOM, which is a much less performant approach. Is this the way how MS currently recommends to face…
78 votesThanks for your feedback! We’re reviewing your suggestion.
- Don't see your idea?