Part 7: Working with Ranges in the Search Refiner Control

This post is over a year old, some of this information may be out of date.

This is an extra post for the search refiner control series. In this post I’ll explain how you could build a search refiner control that makes use of ranges.

The range operator can be used for the following search data types:

DateTime
Decimal
Integer

The out-of-the-box refiner controls use this range operator for its slider controls, but it can easily be used within your custom refiner.

First let me explain the range operator.

Range operator

The range operator requires minimal two values, a start and an end value (Range Operator).

range(start, end)

It’s also possible to apply two optional parameters, an open and close start or end interval.

range(start, stop [,from=“GE”‘“GT”] [,to=“LE”‘“LT”])

With these optional start and end interval parameters, you could specify to include or exclude the start / end values.

From

GE: Greater than or equal to the start value; This includes the start value (Default);
GT: Greater than the start value. This excludes the start value.

LE: Less than or equal to the end value; This includes the end value (Default);
LT: Less than the end value. This excludes the end value.

The range operator can be used with numeric values (integer and decimal) and DateTime values. There are two important things were you should pay attention for:

When using the range operator for DateTime refinement, you should format the dates in ISO format “2013-11-01T00:01:01Z”.
When using the range operator for Decimal refinement, you should let the range operator know that it’s a decimal value. This can be done by using the decimal operator “decimal(10.10)”. Another useful thing, if you don’t want to specify a lower or upper bound, you could use the min or max reserved words as value.

Examples

Integer

1
// Results with the upper bound set to 94
2
range(min, 94)
3
// Results between 20 and 120 (20 and 120 included)
4
range(20, 120)
5
// Results starting from 20 with no upper bound
6
range(20, max)
7
// Results greater than 20
8
range(20, max, from="GT")
9
// Results greater than 20 and less than 120
10
range(20, 120, from="GT", to="LT")

Decimal

1
// Results with the upper bound set to 100.21
2
range(min, 100.21)
3
// Results between 21.21 and 100.21 (21.21 and 100.21 included)
4
range(21.21, 100.21)
5
// Results starting from 100.21 with no upper bound
6
range(100.21, max)

DateTime

1
// Results greater than or equal to November 1st
2
range(2013-11-01T00:01:01Z, max)
3
// Results less than or equal to December 2nd
4
range(min, 2013-12-02T00:01:01Z)
5
// Results from November 1st, until December 2nd
6
range(2013-11-01T00:01:01Z, 2013-12-02T00:01:01Z)

Creating Your Own Range Search Refiner Control

Now that you got a little bit of background information about how the range operator works, it’s time to build our own range search refinement control.

The end result will look like this:

For this search refiner we’ll start from scratch, because the code will be much different than the ones that were created in the previous posts.

The starter’s template looks like this:

1
<html xmlns:mso="urn:schemas-microsoft-com:office:office" xmlns:msdt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882">
2
<head>
3
    <title>Range Filter</title>
4
    <!--[if gte mso 9]>
5
    <xml>
6
        <mso:CustomDocumentProperties>
7
            <mso:CompatibleManagedProperties msdt:dt="string"></mso:CompatibleManagedProperties>
8
            <mso:TemplateHidden msdt:dt="string">0</mso:TemplateHidden>
9
            <mso:CompatibleSearchDataTypes msdt:dt="string">;#DateTime;#Integer;#Decimal;#</mso:CompatibleSearchDataTypes>
10
            <mso:MasterPageDescription msdt:dt="string"></mso:MasterPageDescription>
11
            <mso:ContentTypeId msdt:dt="string">0x0101002039C03B61C64EC4A04F5361F385106604</mso:ContentTypeId>
12
            <mso:TargetControlType msdt:dt="string">;#Refinement;#</mso:TargetControlType>
13
            <mso:HtmlDesignAssociated msdt:dt="string">1</mso:HtmlDesignAssociated>
14
            <mso:CrawlerXSLFile msdt:dt="string"></mso:CrawlerXSLFile>
15
            <mso:HtmlDesignPreviewUrl msdt:dt="string"></mso:HtmlDesignPreviewUrl>
16
    </xml>
17
    <![endif]-->
18
    <script>
19

20
    </script>
21
</head>
22
<body>
23
    <div id="RangeFilter">
24
<!--#_
25
        var listData = ctx.ListData;
26
        var hasControl = true;
27

28
        // Check if the current Refinement Control exists
29
        if ($isNull(ctx.RefinementControl) '' $isNull(ctx.ClientControl)) hasControl = false;
30

31
        if (hasControl) {
32
            // Check if listdata contains data
33
            if(!$isNull(listData) && !$isEmptyArray(listData)) {
34
              // ALL CODE WILL BE WRITTEN HERE
35
            }
36
        }
37
_#-->
38
    </div>
39
</body>
40
</html>

In this starter’s template you’ll find the CompatibleSearchDataTypes property, this property specifies for which kind of search data types that the control can be used. In this control the property is set to be used for DateTime, Integer, and Decimal search data types.

Next step is to create the ID variables for the elements that will be used, and the default refinement control classes.

1
// Element IDs
2
var controlID = ctx.RefinementControl.containerId + "_" + ctx.RefinementControl.propertyName;
3
var fromInput = controlID + "_from";
4
var toInput = controlID + "_to";
5
var refineLink = controlID + "_refine";
6
var clearLink = controlID + "_clear";
7

8
// Show the refinement title
9
var isExpanded = Srch.Refinement.getExpanded(ctx.RefinementControl.propertyName);
10
var iconClass = (isExpanded == "true"? "ms-ref-uparrow" : "ms-ref-downarrow");
11
var refinerCatTitle = Srch.Refinement.getRefinementTitle(ctx.RefinementControl);
12
// Display style > needed to hide the refinement list when collapsed
13
var displayStyle = (isExpanded == "true"? "" : "none");

Now that the variables are created, you can add the HTML mark-up for the refiner. This looks like this:

1
_#-->
2
<div id='Container'>
3
    _#= Srch.U.collapsibleRefinerTitle(ctx.RefinementControl.propertyName, ctx.ClientControl.get_id(), refinerCatTitle, iconClass) =#_
4

5
    <div class='ms-ref-unselSec' style='display:_#= $htmlEncode(displayStyle) =#_'>
6
        <label for='_#= fromInput =#_'>From</label>
7
        <input type='text' id='_#= fromInput =#_' name='from' />
8
        <label for='_#= toInput =#_'>To</label>
9
        <input type='text' id='_#= toInput =#_' name='to' />
10
        <a href='javascript:{}' id="_#= refineLink =#_">Refine</a>
11
        <a href='javascript:{}' id="_#= clearLink =#_">Clear</a>
12
    </div>
13
</div>
14
<!--#_

The output after this will look the same as the end result, but without the functionality.

Adding the Click Events to the Hyperlinks

For the refinement and clear hyperlinks, we’ll add click events via JavaScript. This needs to be done from the moment the search refinement control is loaded. This can be done by using the ctx.OnPostRender functionality.

1
ctx.OnPostRender = [];
2
ctx.OnPostRender.push(function () {
3
    // Retrieve the two hyperlinks
4
    var refineLinkElm = document.getElementById(refineLink);
5
    var clearLinkElm = document.getElementById(clearLink);
6

7
    // Create an onclick event for the refinement link
8
    refineLinkElm.onclick = function () {
9
        // Retrieve the two input fields
10
        var fromInputElm = document.getElementById(fromInput);
11
        var toInputElm = document.getElementById(toInput);
12

13
        // Check if the two input fields contains a value, otherwise nothing needs to be done
14
        if (fromInputElm.value.trim() !== "" '' toInputElm.value.trim() !== "") {
15
            // Retrieve the input values
16
            var fromValue = fromInputElm.value.trim() === "" ? "min" : fromInputElm.value.trim();
17
            var toValue = toInputElm.value.trim() === "" ? "max" : toInputElm.value.trim();
18

19
            // Refinement value
20
            if (ctx.ListData[0].filterTokenType === "decimal") {
21
                fromValue = fromValue === "min" ? fromValue : 'decimal(' + fromValue + ')';
22
                toValue = toValue === "max" ? toValue : 'decimal(' + toValue + ')';
23
            }
24
            // Create the refinement JSON value string
25
            var refinement = '{"'+ ctx.RefinementControl.propertyName +'":["range('+fromValue+','+toValue+')"]}';
26
            $getClientControl(this).updateRefinersJSON(refinement);
27
        }
28
    };
29

30
    // Create a onclick event to remove the refinement
31
    clearLinkElm.onclick = function () {
32
        // NULL Refinement value to remove the refinement
33
        var refinement = '{"'+ ctx.RefinementControl.propertyName +'":null}';
34
        $getClientControl(this).updateRefinersJSON(refinement);
35
    };
36
});

Showing the Refiner Values in the Input Fields

The last step is to show the used refiner values in the input fields after you refined the results. Right now when you do a refinement, the input fields will get cleared.

To add this kind of functionality, we’ll have to retrieve these values from the current refinement category that is in place. This can be done the same way as explained in the previous post (multi-value search refiner control).

1
// Set input form values
2
var from = "";
3
var to = "";
4
var currentRefinementCategory = ctx.ClientControl.getCurrentRefinementCategory(ctx.RefinementControl.propertyName);
5
// Check if the current control refinement is in use
6
if(!Srch.U.n(currentRefinementCategory) && currentRefinementCategory.get_tokenCount() == 1) {
7
    // Parse the current filter token to find the current range condition
8
    var matchResults = Srch.U.parseTypedRangeToken(currentRefinementCategory.t[0], null);
9
    // check for a range token match with corresponding min and max
10
    if (matchResults != null && matchResults.length > 2) {
11
        var from = matchResults[1] === "min" ? "" : matchResults[1];
12
        var to = matchResults[2] === "max" ? "" : matchResults[2];
13
    }
14
}

This code needs to be added just before the HTML mark-up. The refinement values (start and end) that it retrieves will be stored in the from and to variables, and can be used for the input field values by adding a value attribute to the fields.

1
<label for='_#= fromInput =#_'>From</label>
2
<input type='text' id='_#= fromInput =#_' name='from' value='_#= from =#_' />
3
<label for='_#= toInput =#_'>To</label>
4
<input type='text' id='_#= toInput =#_' name='to' value='_#= to =#_' />

Result

The end result looks like this:

Download

This is the complete Range Search Refiner Control Template: Range Search Refiner Control

Blog posts in this series:

Part 1: Create your first search refiner control template
Part 2: Adding Refinement Actions to the Custom Search Refiner Control
Part 3: Working with File Types in the Search Refiner Control Template
Part 4: Create a dropdown refiner control
Part 5: The Search Refiner Control Methods Explained
Part 6: Create a Multi-Value Search Refiner Control
Part 7: Working with Ranges in the Search Refiner Control

Part 7: Working with Ranges in the Search Refiner Control

Range operator

Examples

Creating Your Own Range Search Refiner Control

Adding the Click Events to the Hyperlinks

Showing the Refiner Values in the Input Fields

Result

Download

Blog posts in this series:

Related articles

Part 1: Create Your First Search Refiner Control Template

Part 3: Working with File Types in the Search Refiner Control Template

Part 2: Adding Refinement Actions to the Custom Search Refiner Control

Report issues or make changes on GitHub

Comments

Elio Struyf