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.
-
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
-
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.
318 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.
-
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! 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 focusing on the Microsoft Graph and not the native SharePoint REST API for 3rd party developers.
-
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
205 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.
This is really understandable idea which has been open for a long time, but this is not a focus are for us currently.
-
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.
-
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! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.
This could be potentially exposed in Microsoft Graph APIs in later stage.
-
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.
-
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.
162 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 not evolving the CSOM API surface as such, but would recommend on checking possibility to use Graph API for this scenario at https://docs.microsoft.com/en-us/graph/api/resources/contenttype?view=graph-rest-beta
-
[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
160 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.
Challenge of allowing site owners to embed scripts or CSS is huge security risks which that model enables without centralized coordination/approval at tenant level.
This model was widely adopted in the classic SharePoint from the site owner perspective, but it also caused clear security risks for any tenant where the script embedding was enabled.
SharePoint Framework was designed to address this security concern by only enabling embedding scripts to the modern pages if this is enabled in tenant level by installing a solution which allows that. If this capability is needed – you can absolutely develop your own script embedding web part, but Microsoft is not planning to enable this security issue in modern SharePoint.
We are not also planning to enable embedding CSS styles…
-
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 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 evolving the Microsoft Graph APIs in these areas.
-
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.
-
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 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 potentially to have this in the Microsoft Graph API surface. We have noted this ask in the feature backlog for Graph.
-
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.
-
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! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.
This capability might be enabled in the upcoming vNext on-premises release, but as we are not planning to backport this new feature to SharePoint 2016 level, as requested in the UserVoice entry, we are closing this request.
-
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.
- Don't see your idea?
