Harsh
My feedback
-
3 votesHarsh
shared this idea
·
-
18 votesHarsh
commented
Actually this is helpful when your org is combination of multiple companies
-
20 votesHarsh
commented
Like follow doucment which we had in SP2013
-
4 votesHarsh
commented
more over get back follow document functionality which was avaliable in sharepoint online
-
829 votesworking on it ·
AdminSharePoint UserVoice Admin
(SharePoint UserVoice Admin, Microsoft SharePoint)
responded
We’re working on this! The first web part we’re enabling it on is the News web part, followed by the highlighted content and events web parts. We’d love to hear about other audience targeting scenarios you’d like us to enable. Thanks!
Harsh
commented
The priority is more for quick links more than anything after news
Harsh
supported this idea
·
-
7 votesHarsh
supported this idea
·
-
150 votesHarsh
commented
Good use case can be each division having an hub and these hubsites will be under Common division hub
Harsh
commented
Yes it's an important feature for large org
Harsh
supported this idea
·
-
227 votesHarsh
commented
Too much white space is biggest design flaw
Harsh
supported this idea
·
-
1,074 votesworking on it ·AdminSharePoint UserVoice Admin
(SharePoint UserVoice Admin, Microsoft SharePoint)
responded
As per the Message Center Post MC187289 we have started to roll out Site Swap. This is a new PowerShell cmdlet Invoke-SPOSiteSwap that will enable you to swap your existing root site with a Communication Site. For further information please refer to https://aka.ms/SiteSwap.
Harsh
supported this idea
·
Harsh
commented
How long will we have to wait
-
94 votesthinking about it · 5 comments · Sites and Collaboration » Web Parts · Flag idea as inappropriate… · Admin →Harsh
supported this idea
·
-
23 votesHarsh
commented
In case of document library, you get an error
-
80 votesin the plans · 10 comments · SharePoint Mobile App for Android · Flag idea as inappropriate… · Admin →Harsh
commented
An absolute requirement
Harsh
supported this idea
·
-
1 voteHarsh
shared this idea
·
-
90 votesHarsh
supported this idea
·
-
251 votes
We have started modernizing the search results page a few years ago. It is available on every site under this URL: /_layouts/15/search.aspx/siteall?q=myquery. Also the new search box placed in the suite header has started rolling out to modern experiences, and will be available broadly by end of June. We will be making it available to classic sites later this year as well. Some customers redirect their classic search boxes to the modern results page already.
The modern search experience is a part of the overall Microsoft Search experiences. See more details in this post: https://techcommunity.microsoft.com/t5/Microsoft-Search-Blog/Welcome-to-Microsoft-Search-intelligent-search-for-the-modern/ba-p/531156. We will be bringing additional improvements to it later in 2019, and early 2020 as well including custom refiners, verticals, result types with modern display templates, as well as custom pages that can use modern web parts.
Harsh
commented
Customers are forced to use classic search because of refiners missing in modern search
Harsh
supported this idea
·
-
29 votesthinking about it ·AdminSharePoint UserVoice Admin
(SharePoint UserVoice Admin, Microsoft SharePoint)
responded
Thanks for your feedback! We’re reviewing your suggestion. Remember, the more votes a suggestion gets, the more likely it is that we’ll do it.
Harsh
commented
When searching globally, we need functionality to add custom refiners from search schema like in classic search
Harsh
supported this idea
·
-
67 votestell us more ·AdminSharePoint UserVoice Admin
(SharePoint UserVoice Admin, Microsoft SharePoint)
responded
Thanks for your feedback! We’d like to understand better. It would be useful to know in which cases you think that your customers actually would want to search on the current site?
Harsh
supported this idea
·
Harsh
commented
This is really required, for communicate site it doesnt make sense to search locally
Logically if all sites in hub are related to each other, then it should take the name of hub site.
Because search across sites means search across tenant(org wide search)
Or it can be search across hub..lol
But it's best to pick the name from label "Hub site navigation name" in hub site setting s