Skip to main content

SharePoint 2013 Query Rules

In SharePoint 2013 there are no visual best bets/best bets, keywords replaced with promoted result with Intent based search experience. When condition of query rule trigger based on the rule promoted , result block and result rank applied to the search.

why changed to promoted result?

When client comes and says, I wanted to display my result i.e. promote my results in SharePoint search center what search analysis replay to client, yes we will add visual best bets or best bets. The really client not understand the technical words best bets and also it not make any sense. Microsoft decided to change the visual best bets to “promoted results”.

Query Rules can be created at the Search Service Application, Tenant, Site Collection or Site level.


Query rules composed to three components.

Condition: When to apply the rules?



There are list of condition available, we can create the rule based on the keywords. We can also get the keywords from term store (MMS). For POC purpose I have just created on example with the term "PR".

I have created one Advanced query text match based on the text "PR". Any search term contains word "PR" the below action will performed.


Action: what should do when rules are matched?



when query conditioned matched, Add promoted result ,result block and change the rank result query.

Click Promoted Result Link and below dialog box opened. Give Title, URL and description.


Click Result block link to display result blocks based on the condition. I have created Result block that display only for file having docx extension. With the help of query builder, I created a query.


Publishing: when should the rule active?



After apply the above rule click [OK] to save the changes.

Navigate to the search center and search any term that contains "pr" you will see the promoted result and if term matched with the result block than the result block also display.

Promoted Result Example

Comments

Popular posts from this blog

SharePoint RPC Protocols Examples Using OWSSVR.DLL

What is SharePoint RPC Protocols? Part 1 This reference includes information about the methods and usage of SharePoint Foundation Remote Procedure Call (RPC) protocol. This protocol can be used in Win32-based applications or in ASPX applications to make HTTP POST requests to the server. Methods in this protocol that do not modify the contents of the database can also be used in URL protocol to make HTTP GET requests. Definition taken from http://msdn.microsoft.com/en-us/library/ms448359.aspx You will find the OWSSVR.DLL in SharePoint 2010 Server Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI and MOSS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI OWSSVR.DLL List of commands DialogView  Display ExportList GetProjSchema GetUsageBlob HitCounter RenderView To read more about the OWSSVR.DLL command Please read the URL Protocol from Microsoft Blog having a URL http://msdn.microsoft.com/en...

SharePoint 2013 Search Database Part 1

SharePoint 2013 Search architecture drastically change, as earlier in FS4SP 2010 we have 2 search applications “FASTContentSSA” and “FASTQuerySSA” and 7 total database in use. Following are the List of DB (FS4SP) FASTContentSSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTQuerySSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTSearchAdminDatabase : Fast Search Admin Database  In SharePoint 2013 search has only 1 Search Service application and 4 database in use. No property store database need any more, now the properties are directly stored inside the index component and all the index directly indexed to the physical system where FS4SP data comes from database as well as from the File system now data directly stored and indexed/ retried from the Physical disk because of this performance increase and search experien...

STS CryptographicException Error : Key set does not exist

Common mistakes Both SharePoint Site and SSO Site NOT running on the same application pool. Application pool identity user doesn’t have permission to access the certification.  Solution to this problem Set the same identity pool to  : 2. Be sure to grant rights to the certificate for the App Pool running the web service Start -> Run -> MMC File -> Add/Remove Snapin Add the Certificates Snap In Select Computer Account, then hit next Select Local Computer (the default), then click Finish On the left panel from Console Root, navigate to Certificates (Local Computer) -> Personal -> Certificates You're certificate will most likely be here. Right click on your certificate -> All Tasks -> Manage Private Keys Set you're private key settings here. Add app pool account Reset iis