Forum Discussion
SharePoint Home Page - Modern Search Promoted Results
Thank you so much for getting back to me so quickly.
One clarification : when you say the "all tab searching all of sharepoint / organisation", I'm pretty sure you mean "modern search, Organisation selected, All tab"
https://<mytennant>.sharepoint.com/sites/Test-1Widget/_layouts/15/search.aspx?q=<search term>
GOOD NEWS
This morning when I got in and saw your response , I tested a Teams SharePoint site search in our tennant and it is now showing a best bet I put into the Admin level
https://<mytennant>-admin.sharepoint.com/_layouts/15/SearchAdmin/listqueryrules.aspx?level=tenant&SourceId=<ourcode>
QUESTION
In classic search when a new Query Rule and and Promoted Result (Yes Dean_Gross , you're right I've been around too long and was using very old terminology) is added it appears in Classic search results almost instantly.
Is there a time delay between when a Query Rule and Promoted Result is added at the <mytennant>-admin level, and when it shows up in Modern search ?
A small thing, but for for those of us who have been around for a while something to watch out for.
Again Thanks to you both for getting back to me so quickly.
Really disappointing that the Modern experience is made the default if the core functionality is not there, once again. The user is now asking for his site to be moved to a classic one.
I did eventually find the page stating the differences between Modern and Classic Search, but I think the Product Team have failed to take into account that some organisations have put a great deal of investment into their Search configuration and are therefore prevented from using the Modern sites altogether if it's missing basic features they have been using for years in older versions.
- Dorje-McKinnonNov 17, 2019Iron Contributor
Thanks Geir-Magnus Pettersen for letting us know.
I've done some testing:
- After adding a site level or tenant level Query rule and promoted result I have to wait more than 12 hours for them to appear when the query term matches the promoted result keyword exactly.
Microsoft: is there any way to speed this up, it makes being responsive to the business a bit hard.
- I tested the following
- a site level query rule and promoted result. Called "Sustainability site", keyword sustainability, links to site specific sustainability information
AND
- a tenant level query rule and promoted result. Called "Sustainability tenant", keyword sustainability, links to organisation wide sustainability information
When I search at the site level for Sustainability, both promoted results are displayed (after 12 or 24 hours). With the tenant promoted result above the site one. Same when I click the Organisation link.
Is this how the query rules and promoted results should be working together ?
My way of managing this at present is to only maintain a list of query rules / promoted results at the Tenant level so that I don't have multiple locations to maintain.
Does anyone have a suggestion on other ways to manage promoted results ?
- Robin ThakurNov 13, 2019Copper ContributorThanks @geir Magnus-Petterson, I’ll check it out!
- Geir-Magnus PettersenNov 13, 2019
Microsoft
Promoted results registered on the site level is now available in team sites, comm sites and hub sites.
- Geir-Magnus PettersenJul 16, 2019
Microsoft
When you search from a teamsite by default the search results should be scoped to that teamsite only. Promoted results will not show up on the team site scoped search page.
If you click on the Organization search breadcrumb you should be taken to the tenant wide scoped search results and this should also show the Promoted results that are registered on the tenant level.
We are still working on showing Promoted results on the site level where Promoted results registered on the specific site will show when you are searching scoped to a site. Hope this will roll out in the coming month.
Do you see the expected behavior where the promoted results are shown when you upscope search to Organization?
There is also the option to change search scope from scoped to a site to the organization level. This is explained in this thread