Skip to main content

SharePoint 2013 Search Bound Variables

SharePoint 2013 search architecture almost changed and the new word that I heard today is "Search Bound Variable”. So I deep dive into it.
So the “Search Bound Variable” that you find most of the places during the search configuration & you also wanted to know they it is working and interaction during the query processing.

Search bound variables: The search bound variables are the place holders. So the most common search bound variables are following.

As showing below image in comes the search "cameras images" the {searchboxquery} text is "cameras images". When the query transforms the {searchboxquery} breaks in {subjectTerms} and the "{actionTerms}" to the below example during the query rules the "cameras" is treated like the {subjectTerms} and "images" become {actionTerms}.


As the per the above example in search term "Cameras Images" to explain below how bound variables works.
  • {searchboxquery} : Whatever in the search text box the {searchboxquery} bound variable kept this "cameras Images” value. 
  • {subjectTerms}: As the name suggest {subjectTerms} this bound variable kept the subject term so our case it would be “cameras”. 
  • {actionTerms}: As the name suggest the {actionTerm} kept the end of the sting ie the action need to be taken related to search box text so “Images” would be the action terms. example search term "tv pictures" or "move download" action term is "Pictures" and "download".  
  • {searchTerms}: {searchTerms} keeps changing during the execution process or you can say the query transforms stage. Example during the transformation the serachTerm would something like “cameras contenttype:T site:http://abc/sites/test”. It means the query cameras and content type and site restrictions applied during the query transformation. 

The above Search bound variables also called the query variables and these query variables are showing in the result block. {searchboxquery},{subjectTerms} and {actionTerms}.

1. The Search Bound Variable you can find in during adding the "Result blocks" in Query Rules.


2. The Search Bound Variable you can find in during specified the Query Condition and selecting an option "Advanced Query Text Match" drop down value in Query Rules.


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