Forum Discussion

RobOK's avatar
RobOK
Bronze Contributor
Dec 01, 2017
Solved

Modern - all or nothing?

We are really struggling with how to use the new Modern features. It seems like you have to be all or nothing -- to have a mix of both would be jarring to the users. Is that what people are finding? ...
SharePoint Online
  • Rebekka Aalbers-de Jong's avatar
    Rebekka Aalbers-de Jong
    Dec 11, 2017

    RobOK, you are correct that the default search in a Communication site is only within the site. You can then switch to everything. The Hub site that will come next year will solve this issue. From a Hub site you the search default will be through all connected sites. 

    The Hub site will also solve part of your Navigation issue. It will provide a shared top navigation for all connected sites. Default position of the current navigation of a modern teamsite will stay on the left.

    Structural navigation will not be available though. The key word here is: performance. So you will have to manually create your Navigational nodes.

    Search from a modern site is Microsoft Graph-driven. That simply is very different from classic SharePoint search. If you have highly structured content with lots of content types and heavily used meta deta, than Modern Search will not be very helpful. 

Anonymous's avatar
Anonymous
Dec 13, 2017

Admittedly having not read any of the responses here, one observation I'd like to make is that check in/out is a baaaaaaaaaad practice in SharePoint Online/2016 IMHO.

 

Unless you have an absolute need (the only qualifying ones I can allow in my head are legal or compliance requirements, which is very uncommon), drop the check in/out step in all your [non-automated] business processes. It may have been nice in the past, and it may help keep configuration control a bit more in check, but its value really isn't there when SharePoint offers so many other features that make up for check in/out's disadvantages. The biggest issue is the fact that check in/out is a mutually exclusive concept to co-authoring, which is now the norm.

 

I'd be curious to know what exactly your org's check in/out requirement is and whether it's worth reconsidering for the sake of making sure there are as few bumps in the road as possible. This would also relieve the major complaint you have with the modern UI. (Not all, of course, but that's the one you called out.)

 

I've published an article detailing why I despise check in/out if you're curious to understand in more detail where I'm coming from. http://icsh.pt/SPCheckOut

Resources