Welcome to the Blazor feedback portal. We’re happy you’re here! If you have feedback on how to improve the Blazor, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!


When Syncfusion.EJ2.Blazor control adds items to Syncfusion.EJ2.Blazor.BaseComponent.DataHashTable there is a chance to cause an unhandled exception due to the fact Random.Next() will not always return a unique value; with to my testing was as few as 10 iterations given enough time and proper conditions, even fewer items may cause a key collision.  

Attached is a screenshot of the code I found to be causing the issue in my case however it looks like similar logic of using a single "Random" number to form a needed unique key is used in other locations.

If I may recommend using a Guid instead of a single random number or very least multiple random numbers to form the unique key to mitigate the chances of a collision.