Custom filter development with Kentico CMS

As I couldn’t find any example on how to develop a custom filter in Kentico CMS, I decided to create one for you.
Imagine you have a website displaying game results of your favorite ice hockey league – NHL (OK, maybe my favorite ice hockey league). You have a database table for the team data and another database table for game results. As the number of games in your database grows every day, you suddenly need to allow website visitors to easily filter out only those results that are related to the team they’re the biggest fans of. Therefore, you need to create a filter to display games according to home team name and game date. So, how to do that in Kentico CMS? Develop a custom filter.

How does a filter in Kentico CMS work?

A filter can be connected to a Kentico data source control and used to filter out source data displayed by a connected basic viewer web part(s) (Basic repeater or Basic data list web parts).


Figure 1 Scheme displaying interconnection between filter, data source and viewer web parts.

Filter details

A filter control is basically a standard ASCX user control inheriting from a pre-defined Kentico base class. There are several different classes that your custom control can inherit from. The right base class for your filter depends on what data source you are planning to connect the filter to.

Please review the table below for a list of available custom filter base classes and supported web parts:
Filter base class Works with
CMSAbstractQueryFilterControl Query data source, Custom table data source
CMSAbstractDataFilterControl Document data source
CMSAbstractMenuFilterControl Navigation web parts
NOTE: Filters also work with viewer web parts directly, however, to accomplish the best scalable and optimized solution, we recommend you to use a filter in combination with a data source attached to a basic viewer web part instead.

I’ve prepared sample custom filter controls for every custom filter type (query, data and menu). You can download them along with the export package of my sample website demonstrating their usage and functionality.

Please download the package from here.

The package contains:

1. - website export package,
2. \CMSWebParts – folder contains filter controls code files. Please copy it to the root of your website project folder.

How to actually integrate custom filter in Kentico CMS?

Let’s get back to the requirements from the beginning of this post.

In Kentico CMS Site manager, I’ve first created two custom tables:

1. Team custom table – stores names of home teams,
• Code name:,
• Custom fields: TeamName (Text, 450, Text box),

2. Game custom table – stores information on games played by any of the home teams, result of the games and the date and time of each game,
• Code name:,
• Custom fields: GameTeamID (Integer, Drop-down list), GameAwayTeam (Text, 450, Text box), GameScore (Text, 50, Text box), GameDate (Date and time, Calendar).

I’ve also created the ‘’ custom document type which contains the same fields as the game custom table.

In CMS Desk, I’ve created a new page where I placed the ‘Filter’ web part which is used to load a custom filter control in the Portal Engine (by specifying its ‘Filter name’ and ‘Filter control path’ settings). The page further contains the ‘Custom table data source’ web part loading data from the Games custom table. Data source is connected with the filter through the ‘Filter name’ property which match the ‘Filter name’ identifier set in the filter web part configuration dialog. The template also contains basic viewer web parts like ‘Basic repeater’ & ‘Basic data list’ displaying source data.

Figure 2 Page template displaying filtered data from a source web part using basic viewer web parts.

The whole setup can be summarized as following:

1. Insert the ‘Filter’ web part on the page template. Set the filter unique identifier in the ‘Filter name’ property. Define path to the control in the ‘Filter control path’ property,

2. Place data source web part on page template. Configure data source properties – do not forget about the ‘Filter name’ which should refer to the identifier used for the ‘Filter’ web part from previous step,

3. Use basic repeater or data list to display source data. Do not forget to specify the ‘Data source name’ setting.

Custom query filter

Custom query filter displays two drop-down lists. The first one containing all home teams, the second one with sorting options for results displayed underneath it. In addition there is a filter button which is used to fire filter action.


Figure 3 Filter displayed on the live site with game results underneath.

The filter control initializes its inner controls (drop-down lists) in the OnInit() event like:

/// <summary>
/// Child control creation.
/// </summary>
protected override void OnInit(EventArgs e)



/// <summary>
/// Setup the inner controls.
/// </summary>
private void SetupControl()

if (this.StopProcessing)

this.Visible = false;
else if (!RequestHelper.IsPostBack())

// Load teams options into filter drop-down list
// Initialize sort direction drop-down list

In the InitializeTeams() and InitializeSort() methods, I just retrieve data for selection lists and bind the data.

An important part of the filter comes in the OnPreRender event handler:

/// <summary>
/// Pre render event.
/// </summary>
protected override void OnPreRender(EventArgs e)

// Set filter settings
if (RequestHelper.IsPostBack())



/// <summary>
/// Generates WHERE condition and ORDER BY statement based on the current selection.
/// </summary>
private void SetFilter()

string where = null;

// Generate WHERE condition based on team selected
if (this.drpTeam.SelectedValue != null)

int teamId = ValidationHelper.GetInteger(this.drpTeam.SelectedValue, 0);
if (teamId > 0)

where = "GameTeamID = " + teamId;

// Include sort direction
string order = null;
if (this.drpOrder.SelectedValue != "")

switch (this.drpOrder.SelectedValue)

case "awayasc":
order = "GameAwayTeam ASC";

case "awaydesc":
order = "GameAwayTeam DESC";

case "gameasc":
order = "GameDate ASC";

case "gamedesc":
order = "GameDate DESC";

if (where != null)

// Set where condition
this.WhereCondition = where;
if (order != "")

// Set orderBy condition
this.OrderBy = order;

// Filter changed event

As you can see, based on the selection, filter generates a WHERE condition and an ORDER BY statement which is then used to initialize the inherited WhereCondition and OrderBy base class members. Those members are consumed by the attached data source web part and used in the SQL query. The custom filter control allows data filtering by generating the WHERE condition and passing it to the data control.

Whenever the filter button is clicked post back occurs, control generates WHERE condition and ORDER BY statement and store values in the filter base class members. In the basic viewer web part OnPreRender event the data source is forced to load the content using the WHERE condition retrieved from related filter control.

And that's the way it works. Thank you for your time!

Share this article on   LinkedIn Google+

Karol Jarkovsky

Director of Product


Karol Jarkovsky commented on

Hi Jarek,

The easiest way would be to simply call .Replace("'", "''") on string expression before it's added to the filter WHERE condition.


Jarek commented on

What is the best way to prevent SQL Injection with custom filters? I want to make sure that if someone enters characters which have special meaning in SQL they will not be able to execute commands on my database. eg ' ; ) -- etc

takes entire expressions, not individual values, so I don't see how it is possible to use SqlParameter functionality there. ValidationHelper.GetString() does not seem to be helpful either.

Abdel commented on

Great Post - Thanks