Martin Coupal
My feedback
-
2 votesMartin Coupal
shared this idea
·
-
2 votesMartin Coupal
shared this idea
·
-
1 voteMartin Coupal
shared this idea
·
-
26 votesMartin Coupal
supported this idea
·
-
18 votesMartin Coupal
supported this idea
·
An error occurred while saving the comment -
9 votesMartin Coupal
shared this idea
·
-
5 votesMartin Coupal
supported this idea
·
-
82 votesMartin Coupal
supported this idea
·
-
50 votesMartin Coupal
supported this idea
·
-
2,324 votesworking on it ·
AdminSharePoint UserVoice Admin
(SharePoint UserVoice Admin, Microsoft SharePoint)
responded
We are continuing to make our large list experiences better, please keep the feedback coming.
Spring 2018 update:
- We now support being able to manually add indexes to lists of any size (increased from lists up to 20,000 items previously).
- Starting with the February release of the Office 365 Excel client, you will be able to export your full list instead of getting cut off part of the way through.What we are working on now:
- Predictive indexing will start to work for lists larger than 20,000 items so your views will automatically cause the right indexes to be added to your lists.In our backlog:
- Being able to index/sort/filter by lookup column types (like person, lookup or managed metadata columns) without being throttled.
- Making sure that our REST APIs support querying in ways that will guarantee that the call will not be throttled.For…
An error occurred while saving the comment Martin Coupal
commented
@Jeffrey, you can use Power Query in Excel to get more than 5000 items. Just create a new excel file, go to data tab and get data from SharePoint list data source. You should be ok.
An error occurred while saving the comment Martin Coupal
commented
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.
Martin Coupal
supported this idea
·
-
35 votesMartin Coupal
supported this idea
·
-
28 votesMartin Coupal
supported this idea
·
-
1 vote0 comments · SharePoint Dev Platform » Site Scripts & Site Designs · Flag idea as inappropriate… · Admin →Martin Coupal
shared this idea
·
-
160 votes
An error occurred while saving the comment Martin Coupal
commented
Is someone at Microsoft can give a feedback for this feature request? Not responding to uservoice does not look really professional.
Not having this feature make the web part almost useless in real case business usage.
Martin Coupal
supported this idea
·
-
45 votes
An error occurred while saving the comment Martin Coupal
commented
Hope Microsoft is looking at userVoice... This feature should have been available from the begining.
Martin Coupal
supported this idea
·
-
3 votestell us more ·AdminSharePoint UserVoice Admin
(SharePoint UserVoice Admin, Microsoft SharePoint)
responded
Thanks for your feedback! Are you seeing this in SharePoint Online or an on-premises SharePoint Server version?
An error occurred while saving the comment Martin Coupal
commented
To Microsoft: The issue is with the maptocion api (_api/web/maptoicon) that returns incorrect image url.
For zip file it returns _layouts/15/images/lg_iczip.gif. The image does not exists. Instead it should return _layouts/15/images/lg_iczip.png
For msg file it returns _layouts/15/images/lg_icmsg.png that does not exists. Instead it should return _layouts/15/images/lg_icmsg.gif (However, the issue here is that you should provide the png file...)
-
13 votesMartin Coupal
shared this idea
·
-
69 votes
An error occurred while saving the comment Martin Coupal
commented
Please provide a REAL durable link functionality that support files being moved anywhere in SharePoint. And also provide a real MOVE functionality that is not implemented using a copy & delete.
This lack of crucial features and low vote rate let me think that SharePoint is not really being used as a real, solid EDMS system. Wake Up Microsoft or at least let us know where you are going with this.Martin Coupal
supported this idea
·
-
215 votes
An error occurred while saving the comment Martin Coupal
commented
We should also have the possibility to disable the information panel metadata editing. When using PowerApps with list to do metadata entries, the information panel gives to possibility to bypass PowerApps that could integrate validation logic. I think this could be implement using the "Launch forms in a dialog" list/library advanced options, where "Yes" would force to use the form and disable the metadata update using the information panel. Customizing forms with PowerApps is also supposed to be available for library...
Martin Coupal
supported this idea
·
An error occurred while saving the comment Martin Coupal
commented
Metadata entry in modern page is a non sense. When you open the information panel for a document/list item and edit the properties, each property that you update increment your version number (so when you add a new document, if you have 4 properties to fill out, the version number will start at 5. Completly ridiculous!). If you use the "edit all" option, you need to be very carefull when filling out the properties because if you click outside the properties pane, the panel will close and you will loose your properties updates. This is very frustrating for end user if one of your property is a description and loose the info because you click outside the panel. This add up to other user comments in this thread and there are other issues with modern experience for metadata entry but I will stop here. So my question is: What is all this mess with the modern experience? How come there are not more complaints (are the 100 billons users licenced are really using modern experience with SharePoint libraries? I guess not… so probably why Microsoft is doing nothing about this…). This is unacceptable. Period.
-
937 votes
We initially didn’t enable the full width column on team sites due to the vertical navigation on the left and left justification of team site pages. How do you imagine it should work/look on those pages?
Martin Coupal
supported this idea
·
¸Totally agree. The library default column value will apply the default value on files & subfolders. Document set should do the same.