SharePoint For Developers

2013 search web part encountered an issue  with “ Did you mean ” web part. Actually the main reason when search center page having more the one webpart i.e. content search webpart and it will fire when user fire the query by clicking to the search box. But when some time due to the mistake user enter wrong key word and end up with wrong spelling  "did you mean web part" comes into play and displays the correct word with hyper link. Here comes the issue, when user clicks the hyperlink the search result web part updated as expected but the content search web part not update update as it should be, as per end user experience. The connected webparts with search box  mentioned in my previous post. To overcome this issue, with the help of my friend we come up with below mentioned solution. Recent while working, we faced one interesting issue during the custom development one of our customer raised this issue that “did you mean” not updating others web parts (if more than...

In SharePoint 2010, core result web part having an option to trim the duplicate by edit the core result web part in UI. In SharePoint 2013 the trim duplicate option is hidden and by default(TrimDuplicates:True) and due to this duplicate results not visible in the search result. To enable the search result use need to follow the steps . Export the existing web part. Open the exported web part in notepad and search for “DataProviderJSON” property.  Check “TrimDuplicates” value by default it is true to make visible the duplicate result set its’ value to false. Replace the existing web part with exported one. After done with the above changes might be case of your connection with “Refiners”, “Search box” and “Search Vertical” is disconnected. To make it work correctly you need to modify the search box and set the send query option to “Search Result” and same for refiner web part. More Links SharePoint 2013 Hyperlink Columns recall in search results even it ...

We have created on custom list and this list having columns type text and hyperlink. So we would required to remove the hyperlink column from the full text index search so for that we marked as unsearchable to its managed property and run the full crawl and found that the column is still searchable. Other then this we have remove the crawl property form full text index. The issue is still there. After discussion with Microsoft team it seems that the column . We have escalated this issue to Microsoft. This same issue discussed Mikael Svenson in his post . More Links SharePoint 2013: Enable Duplicate Result in Result Web Part Search box Sends Queries to more then one Control(Search Result & Content Search web part) SharePoint 2013 Search Issues SharePoint 2013 Error: Search has encountered a problem that prevents results from being returned SharePoint 2013 free CodePlex Tools for debug

Question: If you have multiple result web part or combination of search result & content search web part on search result page. The result would be filtered on the basis of the search term and then would be the changes required to modify the search results.  Answer to this Question: First need to identified the number of webparts that takes the input from search box on the basis of our requirement.  Following are the steps that need to get the desired results. 1. Edit Search box web part under "Which Search results Page" Section. The list of search related web part displayed here as per the below image. Only two type of web part will be display here first "Search Result" and "Content Search Web Part". 2. Save the Settings to Click Ok & Save the Web part settings. 3. Change the web part query to get the desired results for each web parts.

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

SharePoint 2013 buzz word "Search 2013 Extensibility" related to the Search prospective. In SharePoint 2013 following are the points where we can customize the search experience.  BCS Connector  Content enrichment web service  Custom entity extraction  Pre/post security trimming  Custom Ranking Models User Experience (UX) BCS Connector : SharePoint 2013 there are some of the new method added in the BCS entity connector framework that works well and more stable for large items. Crawl data from the external system you can use the BCS connector and crawl the data into your SharePoint 2013. Please refer the below link that refer the BDC Mode properties and method that need to incorporate in your BDC file.  SharePoint BCS Connector and its method that required for crawl No Code OData SQL Code .Net Assembly WCF BCS Request Methods  Full Crawl Finder(): Return All Docuemnt SpecificFiner(Id1): Return the properties to the...

Link Database:   This database store analyzes content that is being crawled and added to the search index. The usage information means the user actions or usage events, such as click or viewed items on a SharePoint Site. Link database Stores information extracted by the content processing component and search click information. Store the information based on the click also store the search reports. 1. MSSConfiguration 2. MSSOrdinal 3. MSSQLogO14PageClick 4. MSSQLogPageClick : Query suggestions are automatically generated for a query when users click a result for that same query at least 6 times. Users’ clicks on results are logged and entry pairs of (query, result) are added to the Analytics Link Store DB, specifically to the MSSQLogPageClick table. 5. MSSQLogPageImpressionBlock 6. MSSQLogPageImpressionQuery 7. MSSQLogPageImpressionQueryRule 8. MSSQLogPageImpressionResult 9. MSSQLogPageImpressionResultTemp 10. MSSQLogPageImpressionResultUnproc...

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

Automatically created when site column created and used (the must be stored in the content database using this column). Crawl properties now crated at the site collection level. Earlier only available at the application level. Crawl properties & manage properties created with specific naming convention, as mentioned in the attached link MSDN . Automatically created crawl properties sortable and refinable are turned off and property with text data type. There are list of OOB Manage Properties available at site collection level with different-2 data type start with name Refinable<datatype>00 .. Refinable<datatype>100 to you can use this to make achieve Sorting and refinable by map crawl property one of manage property give it alias.  There is confusion with crawl property, actually in SharePoint 2013 two crawl property created when ever a new site column created and it used. I have created the site column name "MyCustomDate". SharePoint 2013 two ...

Result Types: Each Search result item render differently. In search result page, whatever renders on the page, it is display on the basis of search result and each control has its own result template like Refiners , Core Result, Search Vertical, Search Box  and Hover card . Each item in a search result page use different " Display Template ". Every web part has a option to set result type template. By default SharePoint 2013 comes up with some default list of template.Apart from the search web part there is another web part called Content search web part(CSWP) has its own result template to render the results. Following are the list of default template that are being used by web part. There are may mores display template but I mentioned the common one.  Search Navigation : Search Results Default Search Box: Default Search Box Core Result (Everyone Search vertical): Default Result Refiner control default : Vertical Content Search WP : Control template: ...

Result Source : SharePoint 2013 comes with Result Source, "which is a replacement of SharePoint Scopes and federation locations" . Apply query to transform a corpus subset. In SharePoint 2010, the scopes only are created at the application level to overcome this problem. Result source can be created at Application Level, Site Collection Level and Site Level . Now the every site owner can creates the result source at Application, site collection and site. Site Level Site Collection Level Application Level So site collection result source available to all the sub site, and site can have its own result source. Once it created user create the new Search Vertical and update the core result web part. Following are the steps to create the Result Source. Go to the settings -> Site Settings -> Under Search -> Click to the Result Source -> Click to Add Result Source You need to give the name of the Result Source In Protocol section -> Se...

In SharePoint 2013 the best of two Search Engines “SharePoint Search” and “FAST Search Server for SharePoint” was combined to make one Search Engine that would provide greater redundancy and for better scalability. Microsoft did lots of change in search center as compare with new search center. New search center home page the wide text box without any search tabs i.e.  “All site”, “People”  no more exist. Now the tabs are the part of result page in SharePoint 2013. “ Search tabs ” name changes to “search Vertical”. There are 4 Search verticals default available in search center. Everything: Everything vertical comes all results that includes peoples, content, conversations and videos. The search result depends upon the search term example.  Simple term: Display the result; show the preview in hover cards. There is a option to open document view and edit the item directly. Hover card also display the result directly. People name: If a search term cont...