Editing a recurrent event in the Scheduler with End options set to Never triggers validation on the DatePicker.
This is a regression introduced with R1 of 2022
Never.Validation error is displayed.
screencast
Validation error should not be present in this scenario.
Your recent feature to allow the start and end times to be altered in a timeline view so that you can configure an overnight view is very useful. Could the same facility be provided for the Day, Week and WorkWeek views.
Having the ability to setup a recurrence outside of the scheduler would be nice. The ability to use recurrences for other things that don't make sense showing up on a scheduler. An example would be setting up a an email subscription. I want it to recur, but I don't need to see it on a calendar.
The RecurrenceEditor is a great feature for the scheduler widget. I would also like to use it in other scenarios like a task planer. However such an isolated scenario is currently not supported (ticket answer). In combination with angularJS i.e. I do not have the datepicker correctly displayed.
The recurring events are not rendered as expected in some scenarios depending on the start time set.
The first event is not rendered for every week, but it is rendered for every second week.
When the recurring rule is 'FREQ=WEEKLY' the event should be displayed every week, despite of its starting time.
In 2020 R1 SP2 (2020.1.406) there is a bug related to missing events fixed with 2020.2.513. - Dojo with 2020.1.406
Starting with 2020 R2 (2020.2.513) the current behavior is introduced.
The issue might be related also to: #5978
When the dataSource for the resources is empty and the Month view is selected the 'Cannot read property 'firstChild' of undefined error is thrown in Scheduler.
'Cannot read property 'firstChild' of undefined error is thrown in Scheduler when the Month view is selected.
No error should be thrown with an empty resources dataSource in Scheduler.
The issue is a regression starting with 2020 R1 (2020.1.114) release
When you right click on an event to open a ContextMenu in the Scheduler, the first row is selected.
Regression introduced with 2022.1.301
The first row is selected
The targeted row should be selected
Hi Team,
I'd like to request the Kendo UI Scheduler contain a clearSelection() method within the built-in API.
Thank you!
Currently, the Scheduler widget does not provide the possibility to have different start and end times for its resources. We would like to have the possibility to indicate business hours and timezone per resource.
For example, in the demo linked here we would like Alex and Bob to have different business hours, and also to be able to mark that they are in different timezones.
Setting a required validation message for a date field through the model has no effect.
The custom validation message is not applied.
You should be able to change the message through the model
Is it possible to implement an option to show only the workdays in the Scheduler Month View?
Currently, the default start and end dates in the Agenda view can be edited only if we use a custom view.
It will be very easy for the users if we can just pass these dates as a property.
When setting a timeline view to display as an overnight view have an option to highlight the midnight timeline. This is currently only possible via a complex set of css rules...
you could have something like...
highlightTime: {time: 0, color:#ff0000}
where time is the timeline that needs to be highlighted and color is the color the line should be.
I have a need to create an event that will indicate a resources availability. This only needs to be a thin coloured block. Actual events will then be created along side the 'Availability' block. Basically we have the ability to create an event template. Need to be able to create two have assign the correct template based on what type of event it is. Also need the availability event to be rendered first so that it is always to the left on vertical views and at the top in horizontal views.
Currently the scheduler 'snap' option does not actually snap to the nearest time slot, rather it adjusts the start time +/- the 'majorTick` amount of an event. So an event scheduled at 8:03 am would snap to 7:33 am or 8:33 am, given a 30 minute 'majorTick'. I would be helpful to have another option that allows the event to actually snap to the nearest time slot. So that same 8:03am would snap to 8:00am, 7:30am, or 8:30am.
We can get a string like FREQ=MONTHLY;INTERVAL=2;COUNT=2;BYMONTHDAY=19 but it would be great if there was an option to get a more readable format of the recurrence for labeling purposes (if you cannot already, I cannot find any documentation saying you can). Like, 'Recurring Every 2 months on the 19th, twice' or some such.
Currently, the moveEnd handler contains e.slot and e.resources objects to provide information about the slot where the event was dropped. Please add the corresponding fields to the moveStart handler to identify where the move began.
New edit mode: When events are retrieved, those models should always be as lightweight as possible (id, start, end, title), and not include all the other properties required to edit an event. If you have hundreds of events with lots of properties, your control does not scale well. When you then edit one of these lightweight events, it should make an ajax request to go fetch the "full" model used to populate the edit popup window. For the create, it may not have to make an ajax request, but the "full" schema needs to be defined still, so it has a model to bind, and it would be nice to have a way to dynamically specify that schema, in case you have different event model types. In my case, I have three different types of appointments the user can create/edit. Ideally, these "full" models would either get sent via ajax when the popup is closed, or when the datasource is synced, they get trimmed down to the lightweight version. Hopefully this all makes sense...it's all about having tiny models for speed, but larger models for editing. Anyone that has used your control to show tons of appointments (especially with many properties each) will likely get where I am going with this.