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.
-
SharePoint online Templates
How about having the ability to save templates for SharePoint content, sites and list, regardless if SharePoint is set publish or not.
3 votesThanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now as many of the templates simply cannot be saved as a template as the capability technically cannot be supported.
We are looking into having native support for saving Site Designs from the existing modern sites and there is PowerShell / API level support for templating through SharePoint PnP (open-source) initiatives.
-
Expand CSOM code
Expand CSOM code base so that SharePoint Online users are able to write the same code as on prem users.
3 votesThank you for your input, but since this is too generic statement, item is closed. We are evolving CSOM based on the specific requests and scenarios provided from customers and partners. We are releasing new version of CSOM NuGet packages on monthly basis for SharePoint Online and keep on adding missing scenarios as part of the releases.
Server side object model for SharePoint is massive and there are numerous areas which provide APIs in the farm level. Since CSOM is also used in SharePoint Online, we cannot provide this level of API reach with the CSOM side.
We are addressing gaps in the site and site collection level APIs based on your input, so would suggest to provide input on missing capabilities and to include also the actual business scenario why the API is needed. This helps on prioritizing these requests in the future.
-
In SharePoint communication site please allow developer to add iframe from insecure website (http)
In SharePoint communication site please allow developer to add iframe from insecure website (http)
3 votesThanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now as that would be a security risk and normally all browsers would anyway block mixing both http and https. This is really not even something what we can control in the SharePoint side as it’s dependent on the browser settings.
-
Need expansion of the number of characters that can be used in a REST Call from SharePoint Designer Call Action
The number of characters available before the REST Call returns BadRequest is much too low. This is especially true when using SharePoint Designer Call action to copy a document from one library to another. Another option would be to configure the call for copyTo to use parameters so that the entire call is not required to be in one URL, instead the parameters could be added to a the parameter dictionary
2 votesThanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.
We are no longer investing on the SharePoint Designer experience.
-
Calling list.asmx in sharepoint hosted app
Due to cross domain it won;t call list.asmx service. in app please allow calling list.asmx request
1 voteThanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now
-
SharePoint 2016 certification
Please organize more competitions like #KnowItProveIt and improve certifications learning material availability. Waiting for 2016 certification launch.
1 voteThanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we can act from this system. Your feedback is though noted and bypassed to marketing for possible future competitions.
-
Make the name of the current Composed Look a property of the Web object
Currently there is no simple way to pro grammatically get/set the current Composed Look for a site. The Composed Looks list available from the Site Settings page shows all the looks available, but the only way to determine which one of them is the current one is to tediously compare every item in the list to the one with the name "current", which is inefficient and error prone because if there is a background image as part of the Composed Look, the value in the background image field is changed when the look is chosen by the user so the…
1 voteThanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now. This would absolutely help on the programmatic handling of the site configuration, but we are not currently looking to invest in this area of the branding elements.
-
Worklflow 2013 should have MORE functionality than WF 2010
8pproval Workflow functionality is limited. A ItemModertorStusChanged event reciver is missing. WF 2010 has more functionality and hence used instead of WF2013. Even with WF2010 it is tricky to get appovers names and dates into library columns. SharePoint Designer 2013 is unstable and may corrupt the system!
1 voteThanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now. In SharePoint Online we are gradually moving towards Flow from the classic workflow scenarios. In on-premises workflow is absolutely supported and there should not be any corrupt issues. If that would be the case, it would be rather a bug than a new feature. We do understand the importance of the business processes support and are looking to further invest in this area also in future, but not using the classic concepts.
-
ItemModertorStatusChanged event receiver
ItemUpdated event receiver is a very rough async process that blocks SharePoint functionality heavily. It can't be empty since workflows communicate with SharePoint using it. My Suggestion is to introduce a ItemModertorStatusChanged event receiver. To obtain backwards comptibility, it should be a tick box when creating a workflow in SharePoint Designer to use ItemUpdated or ItemModertorStatusChanged event receiver.
1 voteThanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now. Your suggestion does make sense but would require changes across multiple areas, where we are not currently planning to invest.
-
SharePoint APP with C#
Make it possible to dev SharePoint Hosted Apps with C# (csom) just like JS.
1 voteThanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now. Using C# based customizations in SharePoint Online in safe way was possible in isolated scenarios with Sandbox solutions, but this capability has been removed. SharePoint hosted apps are hosted in the SharePoint and there’s no way to provide code level isolation which would be required for these scenarios.
-
1 vote
Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now through SP dev team. This falls more on the Windows server side enhancements and our team cannot, unfortunately, act on this as such. We do though appreciate your input and agree that TMG was a great product for a purpose in on-premise.
-
Cannot resolve schema file path in manifest.json using SPFx.
When I create a new SPFx webpart, "$schema" path is wrong in WebPart.manifest.json. It must be "client-side-component-manifest.schema.json", but current is "clientSideComponentManifestSchema.json".
1 voteThx for submitting this. This is clearly a bug and should have been already addressed with the v1.2 release. In future, if you have seen any specific bugs or random issues, we would recommend using https://github.com/SharePoint/sp-dev-docs/issues issue list to start a discussion with SharePoint engineering. Uservoice is mainly for the new feature requests and possible issues can, unfortunately, get hidden here. Thx anyway for the submission and please let us know in the issue list if you still have any questions.
-
List-Library Settings Access via CSOM
Provide extra capabilities to deal with SharePoint List settings using CSOM.
Currently some of the properties of List are not accessible using CSOM.
1 voteThanks for your feedback! Although we appreciate your time and effort to give us this feedback, we need to have more specific requests around what’s needed. We would appreciate more specific properties which you need so that we can evaluate exposure of them one-by-one. Thx.
-
Get-PnpTenantSite Enhancements
Get-PnPTenantSite -Detailed -IncludeOneDriveSites
We would like to have the following:
• we would like to be able to target only onedrive sites and/or group sites
• we would like the report to run quickly as per the GUI report in the admin console - that seems to run a similar query in about 2 min.
• we would like a report to show all onedrives / groups / sites created after date1 voteThank you for your input around the SharePoint PnP PowerShell. PnP CommandSets are however not part of the official product, so we support and have a discussion around them in the GitHub. In this case, would suggest creating a new entry to the issue list in the PnP-PowerShell repository at https://github.com/SharePoint/pnp-powershell/issues with these details. Asks are understandable and absolutely reasonable. Do also remember that PnP effort is dependent on the community contributions, so we cannot guarantee on the timelines for addressing any requests.
Thx for your suggestion and time taken for providing us your input.
-
Foooooooopoooooooooole bot
Project bizines teknolezhi and abar clencher and abar news
a ND وقطب بزرگ اطلاعات از تمام شاخه ها و رشته ها1 voteNo idea what’s being asked here, so closing. Thx for your submission, but we can’t help with this.
-
NAPA supporting ECMAScript 2015 or Typescript for both on- and off-premise programming of event receivers
Present programming of Remote Event Receivers is complicated and limited so farm deployed server-side Event receivers are used. Support of ECMAScript 2015 or Typescript is needed in a simple freestanding tool (NAPA?) for both on- and off-premise installations.
1 voteThanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now. NAPA service is no longer supported and the models are moving more towards scenarios with web hooks and Azure functions.
-
A30357714
A30357714
1 voteClosing due inadequate details on the request.
-
Need a telephone number to learn how to repair smoke alarm
Need telephone number to Kidde for troubleshooting smoke alarm.
1 voteHi, since this is not around SharePoint, we’re closing the issue. Please have a look on the Kidde support at http://www.kidde.com/home-safety/en/us/locator/contact-us/.
-
Use Vue.js instead of standard rendering
It would be great to be able to (easily) use something like Vue.js instead of hacking around with XSL or rearranging forms with jquery on PreRender() etc. This would be great for Views too.
Something like Vue.js would also be relatively comprehensible for power business users, not just developers. It could be abstracted too, to make it even easier.
1 voteThanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not precisely something we’re planning to do right now. That refers more specifically on the vue.js usage. You can though use any JavaScript framework in SharePoint Framework implementation. We are looking to enable more flexibility on the list and library templating in future though.
-
SharePoint Hosted APP with Code behind
Allow SharePoint hosted APP to use code behind, keeping the same separation as provider hosted app (separated pool or some docker-like experience)
1 voteThanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now
- Don't see your idea?
