Updated to 19.2.0.46 from 19.1.0.59 and SfPivotView and SfGrid are now causing issues. It is unusable as is without additional checks for the collection being empty. Sample attached to reproduce the exceptions.
SfPivotView produces the following exception:
System.NullReferenceException: Object reference not set to an instance of an object.
at Syncfusion.Blazor.PivotView.Internal.GridColumnHeader`1.c__DisplayClass10_0.BuildRenderTree
b__3(RenderTreeBuilder __builder3)
at Microsoft.AspNetCore.Components.Rendering.RenderTreeBuilder.AddContent(Int32 sequence, RenderFragment fragment)
at Syncfusion.Blazor.Grids.Internal.GridHeader`1.BuildRenderTree(RenderTreeBuilder __builder)
at Microsoft.AspNetCore.Components.ComponentBase..ctor
b__6_0(RenderTreeBuilder builder)
at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.RenderInExistingBatch(RenderQueueEntry renderQueueEntry)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
SfGrid only throws the exception if the datasource is an ObservableCollection<T>, the exception is slightly different but I have bundled them together into one issue due to the similarities in the cause:
System.InvalidOperationException: This operation is only valid on generic types.
at System.RuntimeType.GetGenericTypeDefinition()
at Syncfusion.Blazor.Grids.SfGrid`1.IsObservableCollection(Object data)
at Syncfusion.Blazor.Grids.SfGrid`1.DataProcess(ActionArgs action, ActionEventArgs`1 actionArgs)
at Syncfusion.Blazor.Grids.SfGrid`1.DataProcess(ActionArgs action, ActionEventArgs`1 actionArgs)
at Syncfusion.Blazor.Grids.SfGrid`1.ModelChanged(ActionEventArgs`1 args, Object additionalArgs)
at Syncfusion.Blazor.Grids.SfGrid`1.OnParametersSetAsync()
at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle)
Thanks Rahul, we will check the release on the 21st July to see if it fixes the issues.
Unfortunately, we won't be able to use that version if the bug reported with the SfSchedule control is not fixed.