Martin Coupal
My feedback
-
1,115 votes
The 5,000 item threshold is likely here to stay. We are aware that it takes awareness on both sides to get past this limitation: list owners have to build the right fields, indices, and indexed views so that end user queries can run successfully in large lists. And then, end users have to run the correct queries – they can’t just open the root of the list, they have to use a filtered, indexed view.
We want to pursue work that helps on both these ends – for example, proactively indexing more lists, making suggestions to list owners for views to create that will help end users, and helping end users at query time pick filters that will unblock their queries. Additionally, we want to increase our support for running more types of queries in large lists when an index is present – for example, instead of requiring an indexed…
Martin Coupal
supported this idea
·
-
1 voteMartin Coupal
commented
With the modern UI, when editing item properties of a managed metadata column, the term set dialog provide the ability to add new item even if the column "Allow Fill-in" is set to no (and term set is open).
Martin Coupal
shared this idea
·
-
1 voteMartin Coupal
shared this idea
·
-
123 votes3 comments · SharePoint Dev Platform » SharePoint APIs (CSOM/REST/Server-side) · Flag idea as inappropriate… · Admin →
Thanks for your feedback! We’re reviewing your suggestion.
Martin Coupal
supported this idea
·
Martin Coupal
commented
This is a must and should be used by the PnP Provisioning engine.
-
44 votes
CustomActions that deploy script, JSLinks, and additional web parts on the page are currently not supported in the new experience. Environments that require these unsupported features should continue using classic mode for the time being.
Throughout this year, we will be addressing critical scenario gaps to make the new document library experience support custom processes, commands, and other functionality required for complex, business-critical workflows in complex organizations. Specific capabilities we are investigating building include the ability to host web parts on the page, the ability to define custom view layouts and conditional formatting, and the ability to be visually customized and branded with client-side design packages. In the coming weeks we’ll share additional information surrounding these extensibility opportunities across lists and libraries.
Martin Coupal
commented
This is related to the new library UI experience. Custom Actions are no more available in the UI (ribbon and menu item actions). It needs to be available.
Martin Coupal
supported this idea
·
-
99 votes
CustomActions that deploy script, JSLinks, and additional web parts on the page are currently not supported in the new experience. Environments that require these unsupported features should continue using classic mode for the time being.
Throughout this year, we will be addressing critical scenario gaps to make the new document library experience support custom processes, commands, and other functionality required for complex, business-critical workflows in complex organizations. Specific capabilities we are investigating building include the ability to host web parts on the page, the ability to define custom view layouts and conditional formatting, and the ability to be visually customized and branded with client-side design pacakages. In the coming weeks we’ll share additional information surrounding these extensibility opportunities across lists and libraries.
Martin Coupal
supported this idea
·
Why not enhance and leverage the search engin? You should provide a way to create list/library views based on search and scoped to the list where the results would be presented in a similar layout than a list view (ECB menu etc.).There should be a way to provide real-time search results by using a kind of event driven indexing. This would probably be easier than change how sharepoint stores list data in SQL.