Marc D AndersonMarc D Anderson

My feedback

  1. 4 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)

      We’ll send you updates on this idea

      Marc D AndersonMarc D Anderson supported this idea  · 
    • 8 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        1 comment  ·  Sites and Collaboration » Document Libraries  ·  Flag idea as inappropriate…  ·  Admin →
        Marc D AndersonMarc D Anderson shared this idea  · 
      • 69 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          5 comments  ·  Sites and Collaboration » Navigation  ·  Flag idea as inappropriate…  ·  Admin →
          Marc D AndersonMarc D Anderson shared this idea  · 
        • 97 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            2 comments  ·  Sites and Collaboration » Site Templates  ·  Flag idea as inappropriate…  ·  Admin →
            Marc D AndersonMarc D Anderson commented  · 

            This is something I often add so-called "arbitrary JavaScript via injection" to do in existing list forms. If it were a built-in capability, that would be another reason for script in list forms to be off the table.

          • 16 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)

              We’ll send you updates on this idea

              1 comment  ·  SharePoint Administration » Other  ·  Flag idea as inappropriate…  ·  Admin →
              Marc D AndersonMarc D Anderson supported this idea  · 
              Marc D AndersonMarc D Anderson commented  · 

              This is part of a larger issue around testing and forewarning about upcoming changes. A canary tenant is a nice idea, but having a change log to go along with it would be even better.

            • 140 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                I agree to the terms of service
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                Marc D AndersonMarc D Anderson supported this idea  · 
                Marc D AndersonMarc D Anderson commented  · 

                @André, I've found the behavior you saw in some circumstances. Maybe it's libraries versus lists? My error above is with a list, which for me is at least as common a situation as libraries.

                Either way, the behavior is not as expected, at least for me. I want to be able to get both the ID and Lookup value, just as I can with SOAP.

                Marc D AndersonMarc D Anderson commented  · 

                Bitten by this again today. Argh!!!

                Whenever I run into this, I fall back to SOAP calls, which Just Plain Work.

              • 170 votes
                Vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  I agree to the terms of service
                  Signed in as (Sign out)
                  You have left! (?) (thinking…)
                  6 comments  ·  Sites and Collaboration » Sites Management  ·  Flag idea as inappropriate…  ·  Admin →
                  Marc D AndersonMarc D Anderson supported this idea  · 
                • 1,913 votes
                  Vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    I agree to the terms of service
                    Signed in as (Sign out)
                    You have left! (?) (thinking…)
                    41 comments  ·  Sites and Collaboration » Document Libraries  ·  Flag idea as inappropriate…  ·  Admin →

                    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.

                    Marc D AndersonMarc D Anderson commented  · 

                    I do think the "Working on it" message here should give some hope. Microsoft knows these are issues. If they can't address them and others like them, the flow to O365 will reverse back to on premises.

                    Document Library default views are often built into what amounts to an application, or at least a launch pad into one. It can be anything from simply adding some explanatory text in a CEWP at the top of the page (which is, after all, a Web Part Page) to full fledged functionality provided by additions of DVWPs, JavaScript, CSS, etc. in many cases, the view page ends up looking little like what it started out as.

                    There simply has to be a way to keep these view pages in the mix, as considerable investment of time and money have gone into them. One would hope "telemetry" will show many people *choosing* to stick with "classic" (in this case meaning "functional" and "useful") mode pages, even if all the "Working on it" stuff happens.

                    Change can be good, but not if it undoes past investment and successful implementation.

                    Marc D AndersonMarc D Anderson supported this idea  · 
                  • 881 votes
                    Vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      I agree to the terms of service
                      Signed in as (Sign out)
                      You have left! (?) (thinking…)
                      51 comments  ·  Sites and Collaboration » Document Libraries  ·  Flag idea as inappropriate…  ·  Admin →

                      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…

                      Marc D AndersonMarc D Anderson commented  · 

                      Many times the only reason we need 5000+ items is to do some counts or sums. If those capabilities were there, it would cover a lot of ground. Other times we simply need more than 5000 items. Period.

                      This has always felt like an artificial limitation. In SharePoint 2007, there's no limit and I've built applications that retrieve 20000, 30000+ items using the SOAP services because I truly need to. This is the second decade of the 21st century. If the limit was 100,000 it might make more sense. 5000 is simply way too low. This is especially true since you guys tell us that lists con contain millions of items. If we stuff millions of items into a list and can't retrieve them, then it really defeats the purpose.

                      Marc D AndersonMarc D Anderson supported this idea  · 
                    • 219 votes
                      Vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        I agree to the terms of service
                        Signed in as (Sign out)
                        You have left! (?) (thinking…)
                        Marc D AndersonMarc D Anderson commented  · 

                        I’m totally with you that this type of “non-app” approach needs to be a supported option. The reality is that apps/add-ins are overkill for smaller n, and are out of reach for citizen developers. An approach *like this* would be a step in the right direction if it were "supported".

                      Feedback and Knowledge Base