SharePoint
Feedback by UserVoice

Jay

My feedback

  1. 389 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    76 comments  ·  Sites and Collaboration » Modern Pages  ·  Flag idea as inappropriate…  ·  Admin →
    Jay commented  · 

    Content zone width should be calculated from the browser width and left adjusted to accommodate left navigation dynamically like every other web site.

    MS Admin, this is responsive design 101.

  2. 1,152 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    181 comments  ·  Sites and Collaboration » Modern Pages  ·  Flag idea as inappropriate…  ·  Admin →

    In modern pages, we open links within SharePoint in the same tab by default, and external links in a new tab. In the text web part, users can specify to open links in a new tab, but that isn’t the default behavior. Similarly, for navigation links, they follow the same rule (within SharePoint, same tab, external to SharePoint in a new tab). This is true of the modern web parts that support linking as well (hero, quick links, images, etc.) This is the pattern we’ve adopted for consistency.

    After reviewing other areas of modern sites, like the site pages library, document libraries, lists, site contents, etc. we did find some different opening behaviors which we’ll review and resolve.

    Can you help us understand if this pattern isn’t meeting your expectation, if we have some inconsistencies within modern pages we’ve missed, or if it’s the other areas of modern sites where…

    Jay supported this idea  · 
  3. 1,818 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    180 comments  ·  Sites and Collaboration » Document Libraries  ·  Flag idea as inappropriate…  ·  Admin →
    Jay supported this idea  · 
  4. 1,914 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    149 comments  ·  Sites and Collaboration » Document Libraries  ·  Flag idea as inappropriate…  ·  Admin →
    Jay supported this idea  · 
    Jay commented  · 

    Or dump the atrocious teams experience and consume SharePoint services as they were designed to be used...

  5. 1,344 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Jay commented  · 

    This needs to be desperately addressed as a matter of priority. Throttling should not exist at all.

    Just profiling the SQL calls in order to return a single item is woefully sad. Throttle the speed of the services not the count if its so bad as its made out to be.

    Business I work with have lightening hardware supporting SQL service and were able to safely increase the limit to 500,000. Not a chance they will consider SPO until such a critical bottleneck is lifted.

    Jay supported this idea  · 
  6. 275 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    12 comments  ·  Sites and Collaboration » Sites Management  ·  Flag idea as inappropriate…  ·  Admin →

    A consolidated admin view of where published content types are being used is still being evaluated, but for folks voting for the related use case of “better creation and management of content types” please refer to site designs (aka.ms/spsitedesigns) as a modern mechanism to create/apply content types to site libraries. We are also looking at how this could be more easily supported from hub sites.

    Jay commented  · 

    Well usage property already exists for site content types. It's certainly not hard to implement. I've written a migration script that uses this attribute to see where specific CT's are used then migrate them for various scenarios.

  7. 42 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  SharePoint Administration » Distributed Cache  ·  Flag idea as inappropriate…  ·  Admin →
    Jay supported this idea  · 
  8. 151 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  SharePoint Administration » Taxonomy  ·  Flag idea as inappropriate…  ·  Admin →
    Jay commented  · 

    dont forget content type. "Quick edit" (or after the fact metadat) does not allow you to change the content type.

  9. 1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Jay shared this idea  · 
  10. 95 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SharePoint Administration » Security  ·  Flag idea as inappropriate…  ·  Admin →
    Jay supported this idea  · 
  11. 35 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SharePoint Administration » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Jay commented  · 

    My upvote is to align the product (SharePoint) licensing cost with the service (365) licensing cost. As it stands the only reason I can see is doing this is to drive customers away from their product and into alternatives such as OpenText, Drupal, Joomla etc. (wikipedia has a nice list to start evaluating alternative products)

  12. 5 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SharePoint Search  ·  Flag idea as inappropriate…  ·  Admin →
    Jay supported this idea  · 

Feedback and Knowledge Base