Stefan Bauer
My feedback
-
59 votesStefan Bauer
supported this idea
·
-
47 votesStefan Bauer
supported this idea
·
-
13 votesStefan Bauer
shared this idea
·
-
8 votesStefan Bauer
shared this idea
·
-
368 votesStefan Bauer
supported this idea
·
-
36 votesStefan Bauer
shared this idea
·
-
250 votes12 comments · SharePoint Dev Platform » SharePoint Framework · Flag idea as inappropriate… · Admin →
Thanks for your feedback! We’re reviewing your suggestion. We are looking into closely on the input from the community around this and more specifically around the needed scenarios for the placeholders so that we could also potentially provide also specific customizers based on your requests – rather than just having an empty placeholder. Stay tuned!
Stefan Bauer
supported this idea
·
-
444 votes22 comments · SharePoint Dev Platform » SharePoint Framework · Flag idea as inappropriate… · Admin →
Thanks for your feedback! Just a note to let you know that this is absolutely in our roadmap and we are planning to address this request in future. Good to have though also the vote counts, so that we understand the demand around the request, which helps on prioritizing our internal work.
Stefan Bauer
supported this idea
·
-
260 votesworking on it ·
AdminSharePoint Experiences Team
(spexcustomerengagement@service.microsoft.com, Microsoft SharePoint)
responded
A consolidated admin view of where published content types are being used is still being evaluated, but for folks voting for the related use case of “better creation and management of content types” please refer to site designs (aka.ms/spsitedesigns) as a modern mechanism to create/apply content types to site libraries. We are also looking at how this could be more easily supported from hub sites.
Stefan Bauer
supported this idea
·
Stefan Bauer
commented
Great idea! Not everyone have access to powershell to get that information out and actually this information is already stored with the Content Type Information.
-
45 votes8 comments · SharePoint Hybrid or Migration to Office365 » Other · Flag idea as inappropriate… · Admin →Stefan Bauer
supported this idea
·
-
1,468 votes30 comments · SharePoint Dev Platform » SharePoint APIs (CSOM/REST/Server-side) · Flag idea as inappropriate… · Admin →
Thanks for your feedback! Just a note to let you know that we’re building your suggestion now. We do apologize for the delay on getting this moving, but we are now working on exposing term store operation properly with REST API/Microsoft Graph. We will be covering any updates on the API status, before the actual release, in the SharePoint Dev community calls. Thanks, everyone for your input around this capability.
Stefan Bauer
supported this idea
·
-
2 votesStefan Bauer
supported this idea
·
Stefan Bauer
shared this idea
·
The publishing possibilities shown in the new communication sites serve a great insight of possibilities to create content in SharePoint. While this is an suitable approach for user generated content such as in Wikis there is a high demand to provide a consistent corporate wide communication.
In the past this was possible through page layout option which is now missing and removes the ability for corporate communication departments to manage, plan and organise the content to communicate.
In addition the missing page layout option lead to inconsistent and at least time consuming page creation. It will be hard to recreate the same page again because all asset types and content elements needs to be placed in the exact same order on the new page.From previous project mostly two to three page layout where enough to provide an efficient way to create and orchestrate content creation with enough flexibility. The current page variant selection is not an appropriate equivalent.