Last Updated: 29 Nov 2019 09:37 by ADMIN

In some cases, especially when grouping is involved, the day/week/workWeek views may end up with too many events in a single slot. If the total width of those events could not fit within the slot size, those events will overflow and cover some of their sibling events. To avoid such a result, events rendering in a scrollable container should be considered. This way each event will have a minimum width even if it has too many siblings in the same slot.

Here is a Dojo sample demonstrating the case:

Last Updated: 27 Nov 2019 12:52 by ADMIN


A user deletes an occurence because a few people are ill. Five minutes later the superior enters the office and says the meeting happens anyway. Or the user deletes a wrong occurence.

Resetting the recurrence might not be an option for long running meetings. Like weekly Scrum, project jour fix, ... where the other exceptions should persist. Currently the user has to create a new, separate event.

The exceptions could be rendered as multiselect or list in a separate window which opens after a button click. That way the recurrence editor would not look messy with lots of exceptions.

Last Updated: 08 Nov 2019 08:38 by ADMIN
Currently, the method that selects the events after depends on the events' uids. However, upon data binding, new event elements are created, with different uids. Therefore the corresponding event is not selected.
Last Updated: 01 Oct 2019 07:29 by ADMIN
Created by: Hitendra
Comments: 1
Category: Scheduler
Type: Feature Request

Hi Team,


It would be nice to have a feature of Collapsible / Expandable grouping function like tree view in Kendo Scheduler Timeline view. We have multiple head groups with 100 sub groups which we are not currently able to Expand / Collapse.


Sample Expand / Collpase feature like

File attached for reference.


Thank you.




Last Updated: 28 Jun 2019 08:16 by ADMIN


I'm looking to be able to modify agenda view, so that it is like the group headers in grid - having the date as the group header and then the events that occur on that date shown underneath (also collapsible). Is this possible?

I also tried to do this in the grid but it doesn't seem to work due to the fact that it using a start and an end, not a single date column.




Last Updated: 15 Apr 2019 15:01 by ADMIN
Created by: Brodie
Comments: 1
Category: Scheduler
Type: Feature Request

Hi there,


I would like to know if there is a way to add aggregates to a kendo scheduler?


There is a particular value that I'd like to apply an aggregate.sum to, then have that sum appear in a header. Is this possible with the scheduler? or is there some work around?


Thank you,



Last Updated: 15 Aug 2019 08:13 by ADMIN
Currently events >24h are automatically shown in the all day area. This is confusing if the event starts or ends somewhere during the day. E.g. it starts at 5 p.m. on tuesday and ends on 11 a.m. on thursday.

Noone knows when the resource is really available if the event is shown as all day from tuesday to thursday.

There should be an option to turn that behaviour off and show such events as regular events.

Maybe the only thing needing change is this line in _renderEvents:
var isMultiDayEvent = event.isAllDay || event.end.getTime() - event.start.getTime() >= MS_PER_DAY;
Last Updated: 03 Jun 2019 07:37 by ADMIN
Created by: Michael
Comments: 5
Category: Scheduler
Type: Feature Request
We have a need to be able to provide a dropdown above the scheduler, in order to allow the end user to change the time zone of the scheduler dynamically, even after it has been initialized.  Our team was disappointed that this is currently not possible (, but maybe in the future.  Thanks for reading.
Last Updated: 31 Jul 2019 17:35 by ADMIN
Created by: Max
Comments: 0
Category: Scheduler
Type: Feature Request
In horizontal configuration, with resources displayed down the left side of the control, a large number of resources will cause the control to stop functioning.  In some cases, like ours, we do not have the option to filter the resources by those that have scheduled events, and so infinite scrolling is necessary for the number of resources we need to support. For reference, see the forum post about this here: