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.
-
Provide CSOM and REST API for recurring calendar events
There is no obvious way to get details about a recurring calendar events through the CSOM or REST API.
When querying a calendar list only one item is returned for the calendar recurrence item. Only one field identifies this is a recurring item. the fOccurrence field is a boolean field.
When using the server side object model, properties are available to expand recurring calendar events to get the individual recurring items.
The only way to do this for client applications is to go back to using list.asmx which is not great and I'm not sure how long this will be…
551 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 targeting our API efforts on the Graph API side and due to internal prioritize are not planning to allocate resources to new CSOM capabilities.
If this capability is important for you in the Office 365 platform, we do recommend submitting a specific requests towards Microsoft Graph API changes to address the possible gap.
-
List.NavigateForFormsPages support in CSOM
Currently it's not possible to set the List.NavigateForFormsPages property through CSOM as it is in the server API.
321 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 targeting our API efforts on the Graph API side and due to internal prioritize are not planning to allocate resources to new CSOM capabilities.
If this capability is important for you in the Office 365 platform, we do recommend submitting a specific requests towards Microsoft Graph API changes to address the possible gap.
-
Allow publishing of content type hub content types via CSOM
You cannot currently use CSOM to publish content types in a content type hub in O365. Right now you must imitate the page post back to do it.
286 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 targeting our API efforts on the Graph API side and due to internal prioritize are not planning to allocate resources to new CSOM capabilities.
We are also working on new model for the content type management, which is not aligned with the classic content type hub design which should be soon available.
We do apologize the delay around getting final conclusion on this submission
-
SharePoint 2016 On Premise _api/Web/Lists('listID')/subscriptions support (WebHooks)
Please provide subscriptions API (_api/Web/Lists('listID')/subscriptions support (WebHooks)) SharePoint 2016 On-Premise which helps in webhooks, desktop notifications, mobile/push notifications and cross platform notifications to name a few.
233 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.
Webhook are supported in SharePoint Online and in SharePoint 2019 and even thought they’d absolutely also provide additional value on older versions, we cannot provide them without significant platform changes, which cannot be justified for the older versions.
-
Add information management policy management to CSOM
Add support for managing information management policies, and especially retention policies, on content types and in libraries using CSOM. These are the objects largely in the Microsoft.Office.RecordsManagement.InformationPolicy assembly, such as the Policy, PolicyItem objects, etc.
168 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 targeting our API efforts on the Graph API side and due to internal prioritize are not planning to allocate resources to new CSOM capabilities.
If this capability is important for you in the Office 365 platform, we do recommend submitting a specific requests towards Microsoft Graph API changes to address the possible gap.
-
Add support for sandbox solutions upload and activation in CSOM
You have now announced that no-code sandbox solutions are supported after all. Then you should logically (and quickly) add support for uploading and activating sandbox solutions in the CSOM.
If you at MS are planning to NOT add that support in the CSOM, you should reconsider because:
Customers want to use Save Site As Template. For example, they want to save an OOB team site with some extra lists into a .wsp (=sandbox solution). Then we need to be able to programmatically upload and activate that in a new site collection. Now not possible in the CSOM (except with HTTP…
165 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.
-
Import XsltListViewWebPart definition
It is actually possible to import the definition of a XsltListViewWebPart via LimitedWebPartManager in CSOM. However, not all properties are supported. Important properties like XmlDefinition, Toolbar, ViewStyle, .. are being ignored. There's no possibility to have everything set correctly not even manipulating the backed view after importing the WebPart. Please read also this discussion:
http://sharepoint.stackexchange.com/questions/90433/add-document-library-xsltlistviewwebpart-using-csom-or-web-services157 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 we keep on prioritizing our resources and investments on the modern capabilities.
-
Please add the ability to set column default like you can in Object Model with documentmanagement.dll
Need to do this in CSOM
$columnDefaults = New-Object Microsoft.Office.DocumentManagement.MetadataDefaults($list)
$columnDefaults.SetFieldDefault($Folder.Folder, "TestMMSColumn", "1033;#" + $term.Name + "|" + $term.Id)153 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 targeting our API efforts on the Graph API side and due to internal prioritize are not planning to allocate resources to new CSOM capabilities.
If this capability is important for you in the Office 365 platform, we do recommend submitting a specific requests towards Microsoft Graph API changes to address the possible gap.
-
Provide the ability to identify features that are deactivated using CSOM
It's currently possible to identify the features that are activated at the Site and Web level using CSOM, it isn't however possible to determine which features are present but not activated using CSOM. It would be great if this feature could be added!
149 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 targeting our API efforts on the Graph API side and due to internal prioritize are not planning to allocate resources to new CSOM capabilities.
If this capability is important for you in the Office 365 platform, we do recommend submitting a specific requests towards Microsoft Graph API changes to address the possible gap.
-
Add CSOM support for connected WebParts
At the moment it does not seem possible to create WebPart connections via the Client Side Object Model.
130 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 targeting our API efforts on the Graph API side and due to internal prioritize are not planning to allocate resources to new CSOM capabilities.
We are looking into making this capability potentially to happen in upcoming modern pages API through Microsoft Graph, but are not planning to provide CSOM API for it.
-
Provide the ability to write to Managed Metadata via app-only policy
App-only policy in the SharePoint App Model is very restricted regarding Taxonomy operations. Even if an app is granted full control over the tenant, it lacks the permission to do anything but read operations on Taxonomy. Please provide the ability to create Groups, Term Sets and terms using app-only policy.
111 votesThanks for the feedback. I see this is a duplicate of an already submitted suggestion. So, deleting this duplicate entry.
-
Provide the JSOM API to create SharePoint Site Collections (Tenant Object as CSOM C# has)
In the CSOM C# object model we have the Tenant object that allow us to create Site Collections and do other operations over the Tenant. There is a lack of this piece of the API in the JSOM JavaScript object model. Please extend the JavaScript API with this functionality.
BTW - I would suggest to add a new category as "JSOM Gaps"
106 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 looking into possibly opening up admin REST APIs in the future, but do not have exact timeline for this right now.
-
103 votes
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. We are targeting our API efforts on the Graph API side and due to internal prioritize are not planning to allocate resources to new CSOM capabilities.
If this capability is important for you in the Office 365 platform, we do recommend submitting a specific requests towards Microsoft Graph API changes to address the possible gap.
-
Programmatic way to configure search with CSOM
There's currently no better way to configure search indexed and managed properties than export/import configuration. It's a huge pain when building search related apps and a black box, we need something better
99 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 targeting our API efforts on the Graph API side and due to internal prioritize are not planning to allocate resources to new CSOM capabilities.
We are potentially looking into having Microsoft Graph API operations for the search configuration in the future, but we cannot currently share any ETA for this and capability will not be provided through classic CSOM APIs.
-
Add AlternateJsUrl to SPWeb in all SharePoint models to add JavaScript without customizing masterpage
There is a nice property AlternateCssUrl, by which I can easly add CSS to my site without changing masterpage. I would also like to add JavaScript files (with inheritance) by UI or script, just as I can add CSS files trough AlternateCssUrl
Please Please Please add it!
This would provide a way to create branding without customizing SharePoint masterpages93 votesThank you for your input around this. We have analyzed this request internally and due the direction where we are heading with modern experiences, we won’t be exposing this API in the CSOM side. There will be enhanced options to control branding for the modern team sites. With classic team sites, you should be able to achieve typical scenarios with UserCustomActions or alternatively with custom master pages. We do acknowledge that the API would be useful, but it could also open up additional challenges for the future.
-
Simplify CSOM for using w/Angular/Backbone/Sencha - for Real World Scenarios, use CSS than JS, overcome OData constraints (oriented to CRUD)
All the things are related to SharePoint Online development:
SharePoint CSOM model is too complex for using with leading technologies, such as AngularJS, Backbone, Sencha ExtJS and so on. And there is a lack of documentation for "built-in" CSOM/SharePoint JS API function, for example user name extraction from user field). You have to google a lot to find if anyone has found any solution how to solve it.
There are lots of useless JavaScript that does a lot of functionality/processing that is available using pure CSS or native browser functionality (I'm not talking about HTML5 and CSS3 right now). For…
89 votesThanks for your feedback! Although we appreciate your time and effort to give us this feedback, we can’t really create unfortunately actionable items from this large list of requests. There are extremely valuable items in the text which we would love to get submitted as individual items, so that we can truly triage and address the challenges.
What we are looking is specific actionable items in UserVoice for specific gaps. We can’t unfortunately address collection of items in single efficiently, since improvements will be also released gradually and not as a big bang.
Your input has been absolutely acknowledged, but we’ll have to close this one and would rather request seeing if the specific items or topics have been already submitted as a one-by-one submissions or submit new items.
-
Allow Excel Apps for Office to access cell address of selected cells
Enhance the Office JS API to allow apps to read the cell address of selected cells so a better experience can be provided for users who need to see cell references made via their app. Top priority items should include:
1. The ability to read the cell address of cells a user has selected when using addFromPromptAsync pop up. (e.g. Sheet1!$A$1). This is effectively the same address which shows within the addFromPromptAsync textbox currently.
2. Ability to read cell references of any selected cell/cell range.This enhancement will be useful as currently apps can create a binding to a selection…
74 votesThanks for the feedback. As your feedback is related to Excel Apps, please submit your idea to the Office Excel User Voice forum.
Thanks!
-
Provide ability to deploy and activate master pages to the host web using the app model
One thing that we still use Sandboxed solutions or FTC for is the deploying of branding assets such as master pages. Although, there are some hack-like approaches that you can use with CSOM, a more direct supported approach would be nice.
It would be nice if the model would also set the master page on the host web as well since this is a common piece of code we write as a feature receiver as well.73 votesSince you can upload and activate a master page on the host web using CSOM/JSOM/REST APIs, we consider this scenario to be possible with the existing APIs.
-
Microsoft.SharePoint.Client.AuditQuery in CSOM
It would be good to be able to query the Site Collection Audit data via the client-side object model.
The current Audit Log Reports can serve a purpose, but the real power is being able to query the raw data and generate custom reports. This currently doesn't appear to be available in SharePoint Online and is only available for On-Prem via Microsoft.SharePoint.SPAuditQuery.
62 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.
You can potentially expected similar APIs being introduced at the Microsoft Graph side at some point.
-
Provide the ability to create custom User Profile properties using CSOM/REST
Customers usually creates multiple custom User Profile properties. And there is always a need to script this so that it can be repeated across the environments. Today, the only way is to create these using Web UI. This is a huge problem for customers who are dependent on a large number of custom user profile properties.
61 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 targeting our API efforts on the Graph API side and due to internal prioritize are not planning to allocate resources to new CSOM capabilities.
- Don't see your idea?
