Skip to main content

Changing the position of Search Results Count

At last I got time to play with Display Template. Though this is a simple implementation, this work provided better understanding of customizing the Display template for SharePoint Search results.

The requirement is simple. By default, when you do search, it displays Results Count at the bottom of the page as shown below.

Results Count in OOB Search Page
The requirement is to shown the Results Count at the top just above search results as shown below:
Results Count at top

Let us see how do we achieve this.

Let us first understand how default display template is related. Navigate to Results.aspx, edit page, and edit Search Results web part. You will see something like below.
Search Results Web Part Properties

If you closely look at the "Display Templates" section, there is something called "Results Control Display Template" and it is by default set to "Default Result".

Now, we need to locate the file and modify it to our needs. For this, navigate to Master Page Gallery -> Display Templates folder -> Search folder and here look for Control_SearchResults.html file. Also observe that there is javascript file with the same name. We need to only worry about HTML file and SharePoint will create JS file automatically. Let us not touch OOB file, hence download this file and rename it as "Custom_Control_SearchResults.html".

Open Custom_Control_SearchResults.html in any editor. We need to look at two things here. First, under HTML Title tag, you can see the text "Default Result". This is the text which is shown in web part properties drop down (refer previous diagram). So, change this title to "Customized Default Result".
Next step is to identify the section of the code which is displaying Results count in the page. I just searched for ResultCount and I got the section as shown below. Here, our code of interest is between "ms-srch-resultFooter DIV tag and UL tag.
ResultsCount in Footer

As it is clearly seen, resultscount is within Footer section of the template and hence this is displayed at the bottom. Now, I'll cut these lines and paste them just above "ms-srch-result-groups" DIV tag as shown below:
ResultsCount re-positioned
Save the file and upload it to the same folder in Master Page Gallery from where you downloaded Control_SearchResults.html. In the file properties window, ensure that Content Type is Control Display Template (Actually, since we have taken copy of out of the box display template, most of the properties remains correct) as shown below.
Property
Save this file. Observe that SharePoint has created javascript file with the same name. Don't forget to publish these files.

Now, go back to Results.aspx, edit Search Result web part, under Results Control Display Template you can see the customized display template is shown. Select that, save the page.
Customized Display Template selection
Now do search and you can see the results count just above the results.

Comments

Popular posts from this blog

How to update Person field with multiple values using REST API

Person or Group field in SharePoint is similar to a Lookup field. When you are updating this field using REST API, you need to append "Id" to the name of the column in the body construct. For example, the body construct looks like this:

data: { "__metadata": { "type": "SP.Data.ListNameListItem" }, "Title": "First Item", "PeopleFieldId": "4" };

The highlighted portions should be replaced by the actual List Name and Column Name. In the above example, the REST call is updating a List item with Title and People columns.

How to get the value for user ID ("4" in the above example) needs a separate explanation and that will be my next post!

The above example works fine if Person field is configured to accept only one value. If we change the Person field to accept multiple values, how do we pass more than one value in the REST call? Since we normally separate user names with semicolon in people picker, I…

All about SharePoint List View Styles

Sometimes, there are out of the box features which we tend to ignore and later when we do apply, we are more than happy about the feature which is readily available in SharePoint. One such feature is List View Style. I never thought I would write a post on this. However, whenever I spoke about this with users, people were excited to see the result. That prompted me to write this post.

Instead of getting into only theory part, I will basically take use cases where these styles can be applied and also touch up on on some minor limitations with certain style.

When you are creating/modifying a List view, you will get an option to select View Style. As shown below, there are 8 options available and Default is always set if you ignore this style.


I will take typical Contact List and Announcement List to explian about these styles. Let us go one by one.

Default:
This view, as name suggest, is the default style in a view. This is one of the widely seen style in SharePoint site. This is how it…

Difference between Choice and Lookup fields in SharePoint

When you have to provide users an option of selecting a value from a list, you can go for a Choice field or a Lookup field. Have you ever wondered which one to use and when? Which option should be chosen over other? To address these questions, one need to understand the differences between these two data types in SharePoint. This post outlines these differences to help users decide the appropriate column type based on their needs.

FactorChoiceLookupPermissionTo add values to a Choice field, you need minimum Design permissionTo add values to a Lookup field, you need minimum Contribute/Add permissionChanging existing ValuesIf you change a value in a Choice field, it does not affect the existing values. For example, let us say one of the values was NY and there are items with this value. If you change it to New York in the field schema, it only affects the new values. All existing values will retain NY.If you change a value in a Lookup field, all the existing rows reflect the new value,…