Scheduler Planner/Year view: appointments missing when start month is January (Radzen >= 8.5.0) #1948

New Issue

claunia · 2026-01-29T18:16:00Z

claunia commented

2026-01-29 18:16:00 +00:00

Originally created by @PoKNicolas on GitHub (Jan 12, 2026).

Environment

Radzen (Blazor) library version 8.5.0 and later

Component(s): Scheduler Planner / Year view

Start month: January

Description
Since upgrading to Radzen v8.5.0+, the Planner’s internal start/end time range appears to be calculated incorrectly when the configured start month is January. As a result, the Year view (and/or planner range) does not cover the expected date interval and appointments are not rendered even though they exist in the data source.

Steps to Reproduce

Go to Radzen Blazor Scheduler and select the planner or yéar view with start month January.

Observe the rendered output.

Expected Result
The planner’s visible range (internal start/end timestamps) correctly spans the configured year/month interval starting in January, and all appointments within that range are displayed.

Actual Result
The planner’s internal start/end range is incorrect when the start month is January, while the visible time seems to be correct. Consequently, some or all appointments are not shown. When an additional appointment is created via a click at a day, the preselected start and end times have the wrong year.

Notes

Regression introduced in v8.5.0 (works as expected in versions prior to 8.5.0).

Originally created by @PoKNicolas on GitHub (Jan 12, 2026). Environment Radzen (Blazor) library version 8.5.0 and later Component(s): Scheduler Planner / Year view Start month: January Description Since upgrading to Radzen v8.5.0+, the Planner’s internal start/end time range appears to be calculated incorrectly when the configured start month is January. As a result, the Year view (and/or planner range) does not cover the expected date interval and appointments are not rendered even though they exist in the data source. Steps to Reproduce Go to [Radzen Blazor Scheduler](https://blazor.radzen.com/scheduler?theme=material3#timeline) and select the planner or yéar view with start month January. Observe the rendered output. Expected Result The planner’s visible range (internal start/end timestamps) correctly spans the configured year/month interval starting in January, and all appointments within that range are displayed. Actual Result The planner’s internal start/end range is incorrect when the start month is January, while the visible time seems to be correct. Consequently, some or all appointments are not shown. When an additional appointment is created via a click at a day, the preselected start and end times have the wrong year. Notes Regression introduced in v8.5.0 (works as expected in versions prior to 8.5.0).

claunia closed this issue

2026-01-29 18:16:00 +00:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/radzen-blazor#1948