Microsoft.SharePoint.Client class misses DisplayName, ReadOnly, ShowInDisplayForm properties.

Most important of the first one - DisplayName.
Missing that property leads us to create new field to every single content type as we cannot rename the field which is added to the content type.

Add full API for alerts so you can create, edit and delete alerts for any user through CSOM/REST

Implement SPList.ReadSecurity and SPList.WriteSecurity for client model, like in the server object model.

Currently it is only possible to execute search queries with user context. Allowing for using SharePoint Search with app-only context would make it possible to make better use of the platform and build richer solutions and apps.

Hi,

We've run across a gap in our implementation of the Remote Provisioning model for new Site Collections - the EnableAssignToEmail property on the CSOM List object does not exist. There is no way we can see to automate this setting as part of site creation.

This property corresponds to the Send e-mail when ownership is assigned? setting on certain list types.

In different scenarios (Templating, Migration) it is necessary to access all Information of a list, including content (files, list items, old versions).

An even better approach would be the possiblity of list and content replication, either with or without a manual xml-serialization step in between. Example: List.ReplicateTo(TargetWeb, ...).

The almost perfect solution then also supports exporting / replication of web-page libraries including webparts, all their properties, views, and html page content.

Currently when you deploy an App, any instances of the App will not upgrade until manually done via User Interface. It would be great to be able to Upgrade the App in the App Catalog from the Store or via Side Loading and it upgrade all instances at once.

Remote event receivers have no concept of reliability, or retry in case of failure. If for some reason the Provider-hosted app is unavailable, the remote event receiver will not retry the operation, and that message is lost.

Would love to see the use of a queue or service bus to retry the operation, maybe up to a certain limited number of times. Also would be great to have the failures stored somewhere and exposed so that provider-hosted apps could query for failures and make any necessary adjustments to catch up.

Add the possibility to include or exclude content from an offline synch within CSOM. Like "ExcludeFromOfflineClient" in "SPList.ExcludeFromOfflineClient".

Sample use case :
- You would like to stop the synch of one/several/all Documents Libraries from a site that you would like to archive (i.e. archive stop the offline synch possibility).

Currently, we need to create a sandbox solution with a feature and enable/disable the feature to exclude/include specific lists.

It would be great and useful to have this possibility in CSOM-JS directly.

Best regards,
Daniel

Right now, .json files are still not allowed to be stored in SharePoint Online.

Increasingly a lot of open source tools: github, bower, npm, Visual Studio Code. All wants to store settings in *.json files - this limitation in SharePoint Online makes it impossible to use many of these tools via WebDAV.

CSOM for both Silverlight and JavaScript have an ExecuteQueryAsync method. This is not available for the .NET version.

Currently, ExecuteQuery blocks the current thread and in the context of an ASP.Net application this is very resource intensive - the request thread cannot be used to service other threads whilst ExecuteQuery is waiting for a response.

ASP.Net applications only have a small number of threads proportionate to the number of cores and the lack of async support makes it very difficult to write SharePoint provider-hosted add-ins capable of handling large numbers of concurrent requests.

Currently, the SharePoint Framework solutions are deployed as tenant wide app packages. Thereby, all instances of the web parts refer the JavaScript files from the CDN location specified in the packaged that is deployed in the app catalog. We need the ability to run Development, Staging and Production environments as different Site Collections in the same tenant.

Today CSOM expose ComplianceTag per item in a list/library. The library UI support setting a default ComplianceTag. Having this property in CSOM would be useful for provisioning scenarios.

If you look at the SchemaXml for the list the property is visible.

TypeScript 2.4..... all of the major UI frameworks are in the Industry of UX are rocking 2.8 or higher, even 3. MS you have to stay ontop of this or SPFX will die on the vine.

The full width section on communication pages only allows the hero and images web part. It would be great if we could deploy custom full width web parts that can be added to this section.

Provide the ability to declare/undeclare a record as a record using CSOM. Currently you have to use PowerShell or a farm solution to accomplish this :(

Please preate a @microsoft/sharepoint-2016 SPFx generator, so that I don't have to keep uninstalling the supported on-premesis (@1.0.2) generator, then re-installing the @latest version for SPO. I should have access to both generators at the same time, one supporting the latest on-prem feature pack, and one for the latest SPO environment.

So, the idea to allow Admins or developers access to get; set; existing and new user alerts on a site collection using the Client Side Object Model (CSOM). I can think of a handful of times from a support perspective this would have been handy when assisting end-users or Site Collection Admins. So please allow the CSOM access to the SPUser.Alerts on the site collection context.

Microsoft needs to provide APIs to manage alerts i.e. add/update/delete alerts added against list/list item. In case it is considered as a security breach to allow Admin users to add alerts on behalf of other users and hence the API is still not available, an API to at least modify alerts for the currently logged in user is essential. Currently there is no way whatsoever to add an alert programmatically in client side.