SharePoint For Developers

SharePoint Query suggestions: In this post I am going to share with you code snippets to implement the query suggestion in custom text box. Below are the dependency files  1. Jquery UI : http://code.jquery.com/ui/1.10.0/jquery-ui.js 2. Jquery AutoComplete CSS: http://code.jquery.com/ui/1.10.0/themes/base/jquery-ui.css http://code.jquery.com/ui/1.10.0/themes/base/jquery.ui.autocomplete.css 3. JQuery: http://code.jquery.com/jquery-1.8.3.js Query Suggestion Parameter: Here is the post http://blogs.msdn.com/b/nadeemis/archive/2012/08/24/sharepoint-2013-search-rest-api.aspx that specified the detail query suggestions parameter list. Implementation: I have two vertical examples. 1. People Vertical 2. Everything Vertical I wanted to display the query suggestions on TeamSite pages although my search is configured in one of our serach center, so when user search for a particular term and it contains in the search query completion li...

Today I came around this Result type issue with Multi type Managed Property. I have created one template & I wanted to show this template on particular condition. So I created the result type. The Managed property (MP) that I used, I have verified its attributes all attributes are selected and its type is Multi value. I am trying to apply the " conditions" and somehow the value not matched. I have checked MP ; it has all the values but somehow the template not called. When I removed this condition it working and when choose other MP other then Multi valued . It is working as expected. The details implementation.  Let me explain you more with example. Navigation to the schema link Under the Site Settings -> Site section click to the schema link. Verify that DisplayAuthor having all the required properties selected, the most important it must be Muti value . Next step would be crating the custom template. For that I need to map the drive and create th...

General Guideline: SharePoint 2013 Search Farm installation general guideline. So how would be the search farm structure? To installation each component in farm that you need to analysis the number of item in your organization. So if the content less < 10 mil then 2 index component and 1 partitioned per 10 mil items,  2 Query, 2 content processing, 2 Analytic, 1 crawl database and 1 link database.  For the performance issues: Crawl time and result freshness: Add crawl database and content processing component for improve the crawl time and result freshness. Result time: For query latency add more index replica and for query throughput add more partition    Use the following matrix to configure Search Farm Use 2 Crawl Component  Use 2 Search Administrator Component Number of Analytic database varies depend upon the usage

Today we encounter an issue related to the "Fast Search" missing template. When we creating the site collection by going into the central admin and select the "Fast Search" template the default the "Fast Search Template" feature activated and this template is available for all the sub sites   as well. The problem comes when we creating the site collection other than this template like "teamsite" template. The "Fast Search Template" feature is deactivated by default. So we unable to find the search template under this site collection, for that we would req. to activate this feature manually. So we need to run the following Power shell. $site = Get-SPSite -Identity http://Sp2010/sites/Search $site.Features.Add("5EAC763D-FBF5-4d6f-A76B-EDED7DD7B0A5")

This issue comes when we are deploying WSP solution to our SharePoint Farm. When we activated the solution timer job created with future time. We waited for the timer job to complete but nothing happen still showing deploying. In our farm we have 4 WFE servers we have check many blogs related to this type of issue like mentioned below. http://social.technet.microsoft.com/Forums/office/en-US/93f4cac5-2a9f-4715-8505-62f20f203846/wsp-deployment-status-shows-deployingscheduled-at-date-time-but-even-though-its-already-deployed We check the all WFE servers and found the most of the servers following two services was stopped.  SharePoint Timer  service SharePoint Administration   So I stated both two services in all my WFE servers and the problem solved.

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. {searchbox...

In SharePoint search the most of time people annoying that actual content and search content not in Sync. So the search administrator keeps hitting head on the wall and putting same excuse in front of stakeholders “please wait for the next incremental crawl, most of the time :)”. As we know we already have two content crawling methods first is “ Full Crawl ” and second is “ Incremental crawl ”. Disadvantage of the “ Full Crawl ” and “ Incremental Crawl” as both can’t run in a parallel i.e. the content change during the crawl, it required next incremental crawl. So what is new in continues crawl? The content source that using continues crawl that run in parallel . The default waiting time is 15 min. So the default wait time can change via PowerShell , no UI for that. Now the content is up to date most of the time. This crawler only for SharePoint content source, so the job of the SharePoint administrator need to identify those content which are keep updating on the regular ...

As SharePoint 2010 perform the entity extraction & data cleansing we required the FAST document processing stage called pipeline extensibility stage, it is no longer available. It was replaced by content enrichment web services.  As Microsoft says about it.  Search in SharePoint 2013 enables users to modify the managed properties of crawled items before they are indexed by calling out to an external content enrichment web service. The ability to modify managed properties for items during content processing is helpful when performing tasks such as data cleansing, entity extraction, classification, and tagging.   Please go through with the below links for more details. http://msdn.microsoft.com/en-us/library/jj1639 82.aspx http://msdn.microsoft.com/en-us/library/jj163968.aspx There are some of the good article, that describe the advanced content enrichment web service Advanced Content Enrichment in SharePoint 2013 Search Calling WCF using Conte...

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). ...