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,382 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…
742 votesThanks for your feedback! We’re reviewing your suggestion.
-
Extensions: Application Customizer - Additional Placeholders Requested
Today we get PageHead & PageFooter... would like to have BEFORE/AFTER DIV's for
QuickLaunch
&PlaceholderMain
Cross-reference:
https://github.com/SharePoint/sp-dev-docs/issues/625424 votesWe are actively working on new extensions like covered in SharePoint Conference 2019 breakout sessions. There will be extensions on the page content and ways to replace the native menu experience and/or footer experience.
-
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…
404 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)369 votesThanks for your feedback! We’re reviewing your suggestion.
-
Provide support for LivePersonaCard in 3rd-party solutions
The LivePersonaCard control, which renders a user's full profile card, can be loaded in a SPFx solution with LoadByComponentId. However, it is unclear whether this will be supported in the future.
The PnP reusable controls has a Pull Request to provide developers with a LivePersonaCard control, but it is currently in holding pattern until it can be confirmed that LivePersonaCard (and LoadByComponentId) will be supported.
Please empower 3rd party developers to build rich user-aware SharePoint solutions by providing solution for the live persona card.
Cross-reference: https://github.com/SharePoint/sp-dev-fx-controls-react/pull/353
354 votes -
Official documented Api needed to fetch modern Pages View count
SharePoint modern pages Social bar View count apparently does not use Search Managed property ViewLifeTime or ViewsLifeTimeUniqueUsers. Fiddler traces shows that some Internal Apis are used to fetch modern pages social bar view count. It would great if Microsoft release Public documented API so that custom SPFx web parts/extension in need of modern page view count, could utilize the API
241 votes -
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!
222 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.
-
API support for followed sites
There's an undocumented API (https://tenant.sharepoint.com/vtibin/homeapi.ashx/ ) to follow sites and query data around those concepts. For corporate intranet scenarios, we often want to present the data a different way, surfacing native SharePoint capabilities. In order to add a "follow" button on an SPFX web part, we'd need an API to access that.
Related GitHub issue https://github.com/SharePoint/sp-dev-docs/issues/1689
202 votesThanks for your feedback! Just a note to let you know that we’re building your suggestion now. We did mention this capability in dev keynote at SharePoint Conference 2019 and it’s coming later this year.
-
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.
-
Fix the REST API to return the value and not the Id when getting single value Managed Metadata field
REST API should be fixed when getting single value Managed Metadata since it returns the Id instead of the actual value, which then requires another call to get the value. Without this you cannot show a list of items/docs with the single Managed Metadata value. Note that "Allow Multiple" Managed Metadata works fine as it returns a collection of actual values.
For details see: http://sharepointificate.blogspot.com/2014/05/taxonomy-columns-sharepoint-2013-list.html
159 votes -
Add Web.Recycle method to CSOM
The Web class in the CSOM lacks the ability to send a web to the recycle bin. Currently it's only possible to delete a web by using Web.DeleteObject() which makes restoring from recycle bin impossible.
Please consider adding a Recycle() method to the Web class.
156 votes -
[MODERN PAGES] Add web for adding CSS and Javascript on Sharepoint Modern Pages
Add support for adding CSS and Javascript on Sharepoint Modern Pages.
Here is an example implementation on github, but certainly my organisation will not implement it (straight out of github project), unless Microsoft can push this capability to Sharepoint:
https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-script-editorPlease see this image for more details, where I am trying to suggest adding a new Web Part for Scripts+CSS:
https://i.imgur.com/dtpIzdY.pngThis capability is available in old Sharepoint Pages, so hopefully it should be easy to push in Modern Pages (which I really like to use).
Regards
154 votes -
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.
-
Add CSOM support for Document Set settings on content type
Please consider adding support for setting/retrieving doucment set properties on a content type. We need to be able to set properties like Shared columns, Welcome page and Welcome page view on the document set.
147 votes
- Don't see your idea?