Skip to main content

Customizing SharePoint search results web part

In some cases the client does not want to display/see out-of-the-box search results. For example the client wants to have a search functionality only on a specific document library or wants to see all the related links by a particular author. In this case it makes sense to display the search results grouped by author. Below we will try to display the search results web part grouped by author.

Step 1. In search centre page(where you have placed search box and search results web part), click on ‘Site Actions’ and ‘Edit Page’.

Figure 1. Click on ‘Edit Page’. (Since I have already modified the ‘Search Core Results’ web part, you are able to see group by result.)


Step 2. For ‘Search Core Results’ web part, click on ‘modify shared web part’


Figure 2. Click on ‘Modify Shared Web Part’ for ‘Search Core esults’.


Step 3. Click on ‘XSL Editor…’ button. Copy all the text available. Now open notepad and paste all the content in it. Save the file as ‘SearchAll.xml’.

Figure 3. Click on ‘XSL Editor…’ button and copy the text available.


Step 4. Open SharePoint designer, Open any test site. On the test site, right click and create a new .ASPX page.

Figure 4. Click on ‘New’ -> ‘ASPX’ from the context menu.


Step 5. Open the newly created aspx page and from the menu, click on Data View -> Manage Data Sources.

Figure 5. Click on ‘Data View’ -> ‘Manage Data Sources…’ from the menu.


Step 6. From the ‘Data source Library’ click on ‘Add an XML file’. Browse and select the ‘SelectAll.xml’ file you have saved in step 3.

Step 7. Click on ‘Show Data’ from the xml file you have just now added.

Figure 6. Click on ‘Show Data’ from the context menu.


Step 8. Now drag and drop the columns that you think are necessary for grouping information. For this example, I have selected title, author, size and write.

Figure 7. Drag and drop required columns on to the page.


Step 9. From ‘Common data view tasks’, select ‘Sort and Group’. Now select ‘Author’ from the available fields. And also check ‘Show group header’ property. Click on OK.

Figure 8. Click on ‘Sort and Group’ from the context menu and select ‘author’ from the available fields.


Step 10. For column title, select ‘Hyperlink’ for ‘Format as :’. Say yes to the confirm box. In the ‘Edit Hyperlink’ dialog, change the address as ‘{url}’ and text to display as ‘{title}’.

Figure 9. Select ‘Hyperlink’ from the content menu for ‘Format as:’.



Figure 10. Edit Hyperlink dialog.


Step 11. Go to code of the .aspx page and copy all the content between tags.

Figure 11. Select xsl stylesheet from code.


Step 12. Paste the xsl copied in to the XSL editor dialog box. Click on save and apply.

Figure 12. Paste the code onto the xsl editor.



Figure 13. The result can be seen as above.


-Vighnesh Bendre

Comments

Popular posts from this blog

Error while activating feature - SharePoint 2010

Hi all, While I was working on SharePoint 2010 recently I came across some issues. I am putting them across so that anyone facing the same issue may find solution easily. Error: Error occurred in deployment step 'Activate Features': Feature with Id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' is not installed in this farm, and cannot be added to this scope. Solutions: I was getting this error while ‘deploy’ing a feature from Visual Studio 2010. I searched the entire project for this GUID which is mentioned in the error. I did not find it anywhere. While troubleshooting, I opened the physical folder and opened ‘Feature1.feature’ file in notepad. This xml file was using the before mentioned GUID. I was not able to find it in VS 2010 :( I copied the GUID mentioned in the ‘Feature1.feature’ file and pasted it in the Feature ID section in ‘Feature1.Template.xml’ file. This solved the problem. Why I thought to mention it is because the exception thrown is confusing. It does not tell you...

Working with large xml files in c# .net

Working with large (huge) xml files is always a pain in the … The reason? These files can’t be loaded in to memory. On my desktop, where I have 2 gigs memory, I can’t open the file in even notepad. I was presented with a challenge recently to manipulate one such large xml file. The xml file was of 550+ MB. I know many would say I have seen bigger xml files than this. But the heart of the matter is if I can’t open 550+ MB file in notepad or in xmldocument in c#, then I can’t open any file bigger than this. And hence the logic to play with these files would remain same. The scenario: We have an xml file from which we want to remove a single node without removing its children. In the below sample xml fragment, the node has to be removed. The children nodes, must then be attached to ( node’s parent) node. One Two 100.22 GoodDay 3 4 Five 200.09 Cra...

Custom People Picker (Editor) in SharePoint 2010

[Modified:11 Oct 2010] Now you can find the source code for this example in CodePlex The out-of-the-box SharePoint people picker allows users to select users, SharePoint groups, Distribution Lists & Security groups . Users may accidentally add large AD groups to SharePoint groups and send notifications to hundreds of people. The administrator may want more control over the security of the people picker control. In some scenario the administrator may want to restrict the user to only select ‘users’ or ‘SharePoint Groups’. This can be achieved by creating a custom people picker control which inherits from SharePoint people editor. In below example, we are going to explore creation of custom people picker control, replace the OOTB people editor control, provide a people picker settings page in central administration and create menu to access the settings page in Central Administration. 1. Create custom people picker For creating a custom control (which inherits from SharePoint PeopleE...