Thank 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.

Thx for submitting this inquiry, but since this does not seem to be a feature request, rather a question on supported capabilities, we’ll close this for now. We would suggest to use following resources for getting input on the possible solution design and options.

• https://techcommunity.microsoft.com/t5/SharePoint-Developer/bd-p/SharePointDev
• https://sharepoint.stackexchange.com/questions/tagged/sharepoint

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 do however review and provide input on the SharePoint PnP / Dev community activities and we do suggest on having a look on the activities and open-source projects on this side. See http://aka.ms/sppnp

We are not right now at least planning to share our code as such but will be using SP PnP as a channel to provide patterns and practices for developer activities.

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 no longer investing on the SharePoint Designer experience.

Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not detailed enough for us to perform any action actions.

Closing as this is not an enhancement. It’s a potential issue in existing capability and reporting these in UserVoice is not the right way to get things sorted out.

Hi, 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/.

Closing due inadequate details on the request.

This is absolutely supported and you can have as many extensions or web parts in single solution talking between each other. There are numerous options for the components to communicate with each other. One of such options is demonstrated in following sample in SharePoint GitHub – https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-rxjs-event-emitter. Since this is not really a new feature request, we will close the issue. Would suggest having questions and discussions in StackExchange, GitHub or in SP Tech Community.

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. 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.

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.

This is actually a security feature in the browsers which are blocking mixing https and http requests on the same page and we cannot solve that for you in SharePoint side.

We do acknowledge that moving from classic JavaScript development to more structural industry standard patterns require some changes in your development process, but we absolutely want to standardize and move SharePoint development models aligned with what other platforms do. This changes might feel huge and even step backward, but it’s highly beneficial for the larger customizations. With the SPFx and client-side web parts you also get centralized control and governance, which is not there with random embedded JavaScript models like with Script Editor web part. We absolutely understand your feedback, but looking into adoption numbers (metrics of usage) of the SPFx, there’s really no reasons for us to turn back from this journey which we started a few years back.

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. NAPA service is no longer supported and the models are moving more towards scenarios with web hooks and Azure functions.

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

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. 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.

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.

Classic save site as a template capability was designed in away which is no longer valid implementation style in the cloud.

We are in a journey with the Site Designs and Site Scripts potentially provide end user driven export capabilities, which could be used to achieve similar outcome, but we are not planning to provide classic “Save site as a template” capability in the modern SharePoint sites.

Thanks 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.

Thanks 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.

Thanks 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.

Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, there was no concrete or actionable input on this one.