New to Telerik UI for ASP.NET Core? Download free 30-day trial

Server Filtering

This article explains how to implement server-side filtering for the Scheduler component.

The server-side filtering allows the user to load only the events that are part of the currently loaded View without the need to fetch all the available data from the datasource. The server-side filtering approach is very useful for situations where there are a lot of events/meetings in the database allowing us to fetch the needed data only - leading to better performance and faster loading.

The code snippets below are extracted from a demo project of Scheduler with Server Filtering in ASP.NET Core that can be downloaded from this repository. The current article discussed the more difficult steps of the server filtering implementation. For more details, please refer to the above-linked repository.

Initializing the Scheduler

When initializing the Scheduler that will work with server filtering there are two important things to configure in its DataSource:

  • Set the .ServerOperation configuration to true
  • Pass a Data parameter to the server when reading the events data
.Read(read => read.Action("Read", "Scheduler").Data("getAdditionalData"))

Here is a sample definition:

    .StartTime(6, 30, 0)
    .Views(views =>
        views.WorkWeekView(workWeekView => workWeekView.Selected(true));
    .DataSource(d => d
        .Model(m =>
            m.Id(f => f.TaskID);
            m.Field(f => f.Title).DefaultValue("No title");
            m.Field(f => f.Title).DefaultValue("No title");
            m.RecurrenceId(f => f.RecurrenceID);
        .Read(read => read.Action("Read", "Scheduler").Data("getAdditionalData"))
        .Create("Create", "Scheduler")
        .Destroy("Destroy", "Scheduler")
        .Update("Update", "Scheduler")

Get the Start and End Dates of the Current Scheduler View

To be sure that the server will return only the events visible in the current Scheduler View, we have to pass to it the timespan that is currently visible. The timespan data is sent to the server using the Data parameter mentioned in the above section.

Here is a function that returns the current timespan boundries:

function getAdditionalData() {
    var scheduler = $("#scheduler").data("kendoScheduler");

    var timezone = scheduler.options.timezone;
    var startDate = kendo.timezone.convert(scheduler.view().startDate(), timezone, "Etc/UTC");
    var endDate = kendo.timezone.convert(scheduler.view().endDate(), timezone, "Etc/UTC");

    var startTime = 0;
    var endTime = 0;

    if (scheduler.view().startTime) {
        //optionally add startTime / endTime of the view
        startTime =;
        endTime =;
        endTime = endTime == 0 ? : endTime;

    var result = {
        Start: new Date(startDate.getTime() - (startDate.getTimezoneOffset() * + startTime),
        End: new Date(endDate.getTime() - (endDate.getTimezoneOffset() * + endTime)

    return result;

Configuration of the Read Method on the Server:

Once the result of the getAdditionalData function is passed to the server it receives it in the range variable in the below Read method definition:

public virtual JsonResult Read([DataSourceRequest] DataSourceRequest request, FilterRange range)
    var data = taskService.GetRange(range.Start, range.End);
    return Json(data.ToDataSourceResult(request));

The Start and End properties of the range object are then passed to the GetRange method and it returns all events that are between the start and end date of the client View.

Here is the definition of the GetRange method:

public virtual IEnumerable<TaskViewModel> GetRange(DateTime start, DateTime end)
    var result = GetAll().ToList().Where(t => (t.RecurrenceRule != null || (t.Start >= start && t.Start <= end) || (t.End >= start && t.End <= end)));

    return result;
In this article