Support .NET Core with CSOM1,702 votes
We are still actively working on the needed changes for providing the CSOM API NuGet package also as a .NET Standard version.
This is currently planned to happen on the first quarter of 2020 calendar year.. We do apologize the inconvenience caused by the delays on getting this out.
Currently term store operations are only available via JSOM. It would be nice to see this added to the REST API as well.1,633 votes
We do apologize a delay here, but are actively working on this and we should have an updated status available on summer or autumn 2019 for starting preview of this capability with our customers and partners.
Today we get PageHead & PageFooter... would like to have BEFORE/AFTER DIV's for
We are actively working on new extensions like covered in SharePoint Conference 2019 breakout sessions. There will be extensions on the page content and ways to replace the native menu experience and/or footer experience.
The latest adjustments in the Microsoft Store police allows store's add-in to works with conjunction with another add-in that is available only from the provider. The solution package (.sppkg) build with SharePoint framework is not classified as 'add-in'. Thus, we cannot add add-in in the Store that depend on SPFx solution and there is no way of delivering customizations to the modern page.
I can offered two options for solving this issue: 1) Adjustment of point 4.18 (https://docs.microsoft.com/en-us/office/dev/store/validation-policies#bk_4) from the Store policy to allows SPFx modifications 2) ApPSource store to start allowing .sppkg solution packages to be added310 votes
Just to update the status. We are actively now working on having support for the SharePoint Framework in our store patterns. Can’t provide an exact ETA for this yet, but it’s being actively developed and worked on.
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.202 votes
Great news – We are currently working on documentation and guidance around this option.
Usage of app@sharepoint is supported option to enable write operations for the Managed Metadata with app-only policy.
Official documentation will be updated in upcoming days and we’ll close this item as that will happen. Thanks everyone for your input and persistence around this.
There's an undocumented API (https://tenant.sharepoint.com/vtibin/homeapi.ashx/ ) to follow sites and query data around those concepts. For corporate intranet scenarios, we often want to present the data a different way, surfacing native SharePoint capabilities. In order to add a "follow" button on an SPFX web part, we'd need an API to access that.
Related GitHub issue https://github.com/SharePoint/sp-dev-docs/issues/1689170 votes
Thanks for your feedback! Just a note to let you know that we’re building your suggestion now. We did mention this capability in dev keynote at SharePoint Conference 2019 and it’s coming later this year.
Prior to Modern Pages, we used to connect web parts to send data from one part to another. E.g., select a document from a document library w
Prior to Modern Pages, we used to connect web parts to send data from one part to another. E.g., select a document from a document library and display a preview of it in a Page Viewer web part. It's so annoying that SharePoint no longer has that feature. Modern Pages seem to be less Modern than they should be. It's like a beginner's web page instead of something you can actually do real work in.1 vote
You should be happy to hear that we are working on this capability and it’s already supported with 3rd party web parts. More details will be released using our guidance and social media channels during the first quarter of 2019.
- Don't see your idea?