SharePoint
Feedback by UserVoice

Ryan

My feedback

  1. 871 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)

      We’ll send you updates on this idea

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

      Ryan commented  · 

      "(noting that SQL will never scan more than 5k rows"

      Can you explain why SQL will never scan more than 5k rows?

      Ryan supported this idea  · 
      Ryan commented  · 

      In the 90's we put everything in folders and subfolders. It sucked. Now with SharePoint, we can tag files with metadata and create views to organize our files dynamically. If I have to break up everything into 5,000-item libraries, I'm basically going back to folders again -- the dynamism is entirely lost. YES I KNOW I can create special queries or buy web parts to make it look like everything is stuck back together. But what about my users? They don't understand that stuff, they want it to just work. How do I begin to explain a 5k limit to them, and really, why should I have to? It shouldn't be essential to their day to day.

      > Other times we simply need more than 5000 items. Period.

      Echoing Marc's comments. I just built a Document Center to house my organization's HR files. It works great. But we're already at 25,000 items, and we'll likely be at 100,000 items in a few years. I'm not going to even try to predict how to divide 100,000 items into 5k chunks in a future-proof way. And how would I sell project that to my directors? "Sir, I need probably 50+ libraries, requiring extensive build and training, instead of just the one." "Why?" "Well, you need to know the limitations of Windows Server to understand." I built workarounds for the 5,000-item limit for now, but honestly, if it weren't for SP's retention policies, we wouldn't have considered SP a future-proof storage solution *at all* thanks to this stupid limit.

      The answer is NOT more education. The answer is raising the limit to 1 Million Files. That's your goal. And honestly, the question isn't whether you'll do it, it's which competitor will beat you to it.

    • 32 votes
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)

        We’ll send you updates on this idea

        3 comments  ·  Sites and Collaboration » Modern Pages  ·  Flag idea as inappropriate…  ·  Admin →
        Ryan supported this idea  · 
      • 40 votes
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)

          We’ll send you updates on this idea

          Ryan commented  · 

          +1 Remember, switching browsers also means having to re-authenticate, since they all have their own cookie sets -- what a pain. This lack of feature parity across browsers is viewed by my users as a low-blow by Microsoft, a refusal to cooperate. Do better, Microsoft.

          Ryan supported this idea  · 
        • 66 votes
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)

            We’ll send you updates on this idea

            8 comments  ·  Sites and Collaboration » Document Libraries  ·  Flag idea as inappropriate…  ·  Admin →
            Ryan supported this idea  · 
          • 8 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)

              We’ll send you updates on this idea

              3 comments  ·  SharePoint Administration » Security  ·  Flag idea as inappropriate…  ·  Admin →
              Ryan shared this idea  · 
            • 214 votes
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)

                We’ll send you updates on this idea

                Thanks for your feedback! Your idea sounds interesting, but we need more information to understand. Can you tell us more about how you would like to use this feature?

                Is your primary intent to use these logs for reporting and for troubleshooting? Will collection and centralization of these logs in a DB, such as the usage DB, provide the functionality that you seek (if these logs contain data of who performed the action, what the action is, what the target of the action, and when the timestamp of the action is)? How important is having a UX, in addition to the centralized log location, on a scale from 1-5 (1 being least important, 2 being somewhat important, 3 being neutral, 4 being important, 5 being not important)?

                Ryan supported this idea  · 

              Feedback and Knowledge Base