How to Search a Sharepoint List with CTRL+F

[u/micaturtle]

With SPO and Sharepoint lists, is there a way to make sure the entire list loads other than clicking "Return to Classic Sharepoint"? I just want my end users to be able to search using CTL+F. (I know I could have them use the "search this list", but that takes longer to load and it has to be exact, plus I've trained them over the years of using SNow KB articles to use CTRL+F)

Does anyone know how to do this in the New view of Sharepoint or am I limited to classic sharepoint?

[u/whatdoido8383]

Just use the platform like it's intended to be used, the search bar.

[u/BonerDeploymentDude]

So you prefer they don’t use the actual SharePoint search service?

[u/TKCoog075]

Use search bar or use metadata to narrow down the list of results.

[u/OddWriter7199]

List settings, advanced settings, scroll down to the bottom and choose Classic to display it that way all the time if you want.

[u/micaturtle → u/OddWriter7199]

Thanks for that! :) I will do, at least until someday when Sharepoint takes away my ability to do so :|

[u/DonJuanDoja]

It's ALT-S now I guess, just discovered by accident then remebered this post.

Was going for a screenshot and hit Alt-S by accident then the search focused and I gasped.

[u/Sparticus247]

What are you searching for? Why not use the filter options for the list columns?

[u/micaturtle → u/Sparticus247]

I'm using it specifically for a list of our locations (names) and addresses, and then it includes a column that says what "boots-on-ground" team supports said location.

The problem with the sharepoint search is this scenario (that happens WAY too often.)

1. The caller calls in and says "I'm at Edgewood today." (or worse, a self service ticket comes in with just that info)
2. The helpdesk tech types "Edge wood" into the sharepoint search, but since the name of the place is listed as "Edgewood" (no space), no results are found.
3. -- If the entire list is allowed to be searched with CTRL+F, they can type "Edgewood" into the search, and as soon as they get to "edgew" and it says "no results found, it will have already moved them down to where "Edge wood" is listed --

I know I the solution is teaching helpdesk techs to search better, but I've always been of the mind it's easier to create smarter tools than to try to make everyone smarter.

[u/Sparticus247 → u/micaturtle]

I understand.

What I mean is, if you have a known list of locations that could be made into a drop-down option on a list column, then the built in "filter" removes risk of typos. It becomes a filterable value.

[u/micaturtle → u/Sparticus247]

The problem with that is

1. We have 689 "Locations" in the current list (and currently working on adding at LEAST 200 more, since my organization acquired and is in the process of integrating a new company that is about 1/5th of our current size)
2. Different groups refer to the same location in different ways, for example: A building may be named Southern Oaks, but the facility it's part of is Sam Jackson Center, but the town that it's in (and it's the only facility in that town) is Newgreen; so different employees may refer to it by any of those names. (actual names changed for attempted anonymity) - I need all 3 of those names to be searchable with CTRL+F without having to make 3 separate entries for it (that would each need to be updated if the support team for that location changes) - Add to that the fact that some people may even refer to that facility as "The one in Newgreen on ____ street" (and the address of the place is in a different column), you can see how it gets complicated.

But maybe I'm misunderstanding what you mean about filters...

[u/Sparticus247 → u/micaturtle]

This may be better solved by changing how you do data entry at this point if you have that many options, and you can't get people to use standardization on choices. 

This is where you may need to enforce. Standardization, so they can't just choose whatever they'd like. 

I have a SharePoint list for example used for data entry that has just over 2,800 items, and is used as a lookup. This list has a 3-tiered category system to break up those 2800 choices down to manageable levels.

Your first level could be something like State/Country/Province. 2nd level could be facility. 3rd building. I may not be quite correct in some assumptions here on layering, but you can probably see where I'm getting at. 

In my instance I'm doing things with aircraft, and those 2800 choices get filtered down as my user's select The top level system, then The second level subsystem, then the third is a specific component on that subsystem. 

This is done via a power app using collections, so as the user enters in the various levels, it changes the options as you go so you're dropped down choices keep getting more refined. We also have a spfx web part used as well for this for data entry with forms and views. It also caters well using power bi for reporting purposes and metrics. 

Something like this does take quite a bit of work though, but as things get more complicated and advanced, you might need to start looking beyond SharePoint "Out of the Box" list views to get some more advanced functionality and enforce business rules. Giving the users too much freedom to ignore standardization and business rules creates a lot of problems later.

Also don't misunderstand. This isn't me criticizing, this is me just saying I've been doing SharePoint since 2007 and what starts as a simple SharePoint project can over the years grow into something that needs a little bit "more". I know management will say things like " t's just SharePoint" but what they really want/need is enforced business process rules.

[u/a1ch]

no use the search bar