Skip to content

81048: Appointments were Missing After Selecting Specialist - #38

Merged
VengateshManiraj merged 1 commit into
syncfusion:masterfrom
VijayakumarRSF4470:ES-81048-AppointmentDisappear
Jun 1, 2026
Merged

VengateshManiraj merged 1 commit into
syncfusion:masterfrom
VijayakumarRSF4470:ES-81048-AppointmentDisappear

Conversation

@VijayakumarRSF4470

@VijayakumarRSF4470 VijayakumarRSF4470 commented May 29, 2026 •

Copy link
Copy Markdown

Bug description

Ticket - 81048: Appointments were Missing After Selecting Specialist.

Root cause

The Syncfusion Scheduler component maintains its own internal data cache when you update properties. the Scheduler doesn't automatically detect these changes and re-render its appointments. The component's internal state remains unchanged.

Solution description

Explicitly call RefreshAsync() to force the Scheduler to re-read the updated properties and refresh its internal cache. In Blazor Server specifically, add a 50ms delay before calling RefreshAsync() because property updates must travel from server to browser via SignalR network communication, and without the delay, the Scheduler refreshes before receiving the new parameter values from the server.

Code Studio usage(Mandatory)

  • Code Studio used in this PR/MR?

    • Yes
    • No
  • If Yes: Primary use (choose one)

    • Generate new code
    • Refactor/improve existing code
    • Tests
    • Bug fix / debugging help
    • Docs / comments
    • Review assistance (explanations/summaries)
    • Other:
  • Outcome

    • Saved time
    • Neutral
    • Cost time
  • If “Cost time” explain in short (1 or 2 lines):

Impact assessment

  • Low - Affects a single feature with minimal user impact
  • Medium - Affects multiple features or has moderate user impact
  • High - Critical functionality or significant user impact

Reason for not identifying earlier

Missed to test this scenario previously

Areas tested against this fix

  • Verified rapidly changing the dropdown item. Ensured appointments were rendered fine.

Breaking changes

  • Yes (Tag breaking-issue)
  • No

If yes, provide breaking commit details link and migration guidance.

Regression testing

  • Verified fix doesn't reintroduce previous bugs
  • Checked edge cases and error scenarios

Action taken to prevent recurrence

  • Added/updated unit tests
  • Other (specify): _________________
  • NA

Automation status

  • BUnit (provide PR link: _________________)
  • Playwight (provide PR link: _________________)
  • NA

Cross-platform verification

  • Blazor Server
  • Blazor WASM
  • NA

Related issues

Is this issue present in EJ2 or other components?

  • Resolved in EJ2 (PR link: _________________)
  • Created task for EJ2 (Task link: _________________)
  • Needs attention in other components (tag needs-attention-coreteam)
  • NA

Output screenshots

Before Fix

chrome_lMi8ByLbAD

After Fix

chrome_7HE8uMTCh2

API changes

  • New API added (API Review task link: _________________)
  • Existing API renamed/modified (API Review task link: _________________)
  • No API changes

Performance verification

  • Verified no memory leaks introduced
  • Verified no performance degradation
  • Not applicable

Reviewer Checklist

  • Reviewed the provided Code Studio usages related information.
  • Code changes follow component guidelines
  • All provided information reviewed and verified
  • Solution addresses the root cause effectively

@VengateshManiraj
VengateshManiraj merged commit a953f57 into syncfusion:master Jun 1, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants