SharePoint Dev Platform
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.
-
Add managed metadata term store operations to REST API
Currently term store operations are only available via JSOM. It would be nice to see this added to the REST API as well.
1,466 votesThanks for your feedback! Just a note to let you know that we’re building your suggestion now. We do apologize for the delay on getting this moving, but we are now working on exposing term store operation properly with REST API/Microsoft Graph. We will be covering any updates on the API status, before the actual release, in the SharePoint Dev community calls. Thanks, everyone for your input around this capability.
-
Support .NET Core with CSOM
Support .NET Core with CSOM
958 votesThanks for your feedback! Just a note to let you know that we’re building your suggestion now. Just to be precise, we are looking into having a .NET Standard version of the CSOM package, so that it’s usable in both older .NET versions and also in the .NET Core. No ETA at this point, but happy to inform that work is in progress.
-
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…
677 votesJust a status update to follow up on the progress. We have now single part app pages in preview starting from SharePoint Framework 1.7 release. We are looking into releasing the initial capability during the first quarter of 2019 calendar year and we’ll continue evolving this based on your input.
You can find more documentation on the currently available preview capability from the following location – https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/single-part-app-pages.
-
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
438 votesThanks for your feedback! Just a note to let you know that this is absolutely in our roadmap and we are planning to address this request in future. Good to have though also the vote counts, so that we understand the demand around the request, which helps on prioritizing our internal work.
-
REST API citizenship! (surface, roadmap and change log)
Besides the lack of detailed documentation around the REST API, given its importance as a major entry point for apps, it needs to be treated with more respect as a service offering. It's currently being updated in CUs and on SharePoint online without any notification of the changes being made (such as the $metadata endpoint appearing - was it in the August 2013 CU for on-prem?). We either need it to be released in a non-breaking change model (URL versioning such as the Twilio model), or messaging needs to be improved so we know when things are going to be…
238 votesThank you for your input. REST APIs are absolutely critical for the SharePoint Framework and for other customizations. We are working on improving the existing documentation and to ensure that you can more efficiently take advantage of the SharePoint REST APIs in your development.
-
Prior to Modern Pages, we used to connect web parts to send data from one part to another. E.g., select a document from a document library w
Prior to Modern Pages, we used to connect web parts to send data from one part to another. E.g., select a document from a document library and display a preview of it in a Page Viewer web part. It's so annoying that SharePoint no longer has that feature. Modern Pages seem to be less Modern than they should be. It's like a beginner's web page instead of something you can actually do real work in.
1 voteYou should be happy to hear that we are working on this capability and it’s already supported with 3rd party web parts. More details will be released using our guidance and social media channels during the first quarter of 2019.
- Don't see your idea?