SharePoint
Feedback by UserVoice

Anonymous

My feedback

  1. 229 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    25 comments  ·  Sites and Collaboration » Web Parts  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    Every cms on the planet has this functionality, except of course modern SP. Ridiculous!

  2. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint Administration » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  3. 2,317 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    236 comments  ·  Sites and Collaboration » Document Libraries  ·  Flag idea as inappropriate…  ·  Admin →

    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
    Anonymous commented  · 

    Since other online storage services don't have this problem, it's pretty clear it's caused by the way SP gets data from the db. SP is an antiquated server based platform probably not well suited to online use in its current form. The idea that SP has to request all items in a list to return a filtered view of say 25 items is absurd. The filtering should happen before the request gets sent but SP simply doesn't work that way and until it's modernized (or in typical Msft fashion, replaced), it's not fit for enterprise use.

    Anonymous supported this idea  · 

Feedback and Knowledge Base