SharePoint
Feedback by UserVoice

Shogo Akimoto

My feedback

  1. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Shogo Akimoto supported this idea  · 
  2. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Sites and Collaboration  ·  Flag idea as inappropriate…  ·  Admin →
    Shogo Akimoto shared this idea  · 
  3. 52 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  SharePoint Hybrid And Migration » Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
    Shogo Akimoto supported this idea  · 
  4. 1,419 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    157 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…

    Shogo Akimoto supported this idea  · 
    Shogo Akimoto commented  · 

    Yes, this is the lock escalation limit on the SQL Server. But expect to impliment other ways (like paging) for removing this limit even if it will be performance down.

Feedback and Knowledge Base