1. Feedback
  2. Blazor
  3. 42055

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!

1
Vote

Persistated SfGrid crashes if count of columns changed

If you´re using the persitated functions in SfGrid component this will raise an exception if the count of columns changed (e.g. code changes or after permission changes).


If the column count do not match the persitated column count anymore this should reset the persistation but not crashes the app unhandled.


Browser exception:


Error: System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index')

   at System.Collections.Generic.List`1.get_Item(Int32 index)

   at Syncfusion.Blazor.Grids.SfGrid`1.PersistProperties(String properties, Boolean isResetPersistData)

   at Syncfusion.Blazor.Grids.SfGrid`1.PersistProperties(String properties, Boolean isResetPersistData)

   at Syncfusion.Blazor.Grids.SfGrid`1.OnAfterScriptRendered()

   at Syncfusion.Blazor.SfBaseComponent.OnAfterRenderAsync(Boolean firstRender)

   at Syncfusion.Blazor.SfDataBoundComponent.OnAfterRenderAsync(Boolean firstRender)

   at Syncfusion.Blazor.Grids.SfGrid`1.OnAfterRenderAsync(Boolean firstRender)

   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)


If columns has been changed persistation state is no longer useful and should be reset.


To reproduce:

  1. Ensure browser cache is enabled and will not be deleted after closing
  2. Create a SfGrid with 3 columns and endable persistation
  3. Start app and open page including SfGrid
  4. Change code -> remove one column
  5. Restart app and open page again => unhandled exception!