Broken after 20.0.3.49 update, had to downgrade to 20.0.3.48.
I was able to reproduce the error and included the sample in web assembly
blazor.webassembly.js:1 crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
Unhandled exception rendering component: Value cannot be null. (Parameter 'json')
System.ArgumentNullException: Value cannot be null. (Parameter 'json')
at System.Text.Json.JsonSerializer.Deserialize[InitialClientModel](String json, JsonSerializerOptions options)
at Syncfusion.Blazor.Layouts.SfDashboardLayout.Initialize()
at Syncfusion.Blazor.Layouts.SfDashboardLayout.OnAfterRenderAsync(Boolean firstRender)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)
window.Module.s.printErr @ blazor.webassembly.js:1
Hi Pavel,
Greetings from Syncfusion support.
In our release version 20.1.47, we have included some of the breaking changes. We suspect that the reported issue at your end is occurring due to this. Please check the below release notes for changes.
Release notes link : https://blazor.syncfusion.com/documentation/release-notes/20.1.47?type=all#common
To overcome the issue, add the below script reference.
<script src=https://cdn.syncfusion.com/blazor/20.1.47/syncfusion-blazor.min.js type="text/javascript"></script> |
Sample : https://www.syncfusion.com/downloads/support/directtrac/general/ze/DashboardWASM-1538581234.zip
You can install the latest individual NuGet package in your sample and add script and style references and avoid JavaScript isolation to overcome the issue. For your reference we have attached the sample. Please check the sample and get back to us if you need any further assistance.
Regards,
Leo Lavanya Dhanaraj
Hi,
I updated to .52 today and still got the failure. I presume you mean that we need to downgrade the script reference to .47 to workaround this issue.
Isn't this waiting to create more compatibility issues, given that the current script reference still fails?
Is there a permanent, complete solution coming, and we should wait if we can, or are we being advised to update to .52, use .47 scripts, and hopefully don't have further problems?
Please advise.
Regards,
Phil
Hi Phil,
We have validated your reported issue in the Blazor Dashboard Layout component. However, we were unable to reproduce the issue you mentioned. Here, we have attached a sample with the latest version and a video footage of the behavior for your reference. Also, we suggest you render the panels with the unique panel id, row and col values in the Dashboard component and clear the NuGet cache maintained in your sample.
Check the below Documentation and sample links.
Documentation : https://blazor.syncfusion.com/documentation/dashboard-layout/panels/position-sizing-of-panels
Sample: https://www.syncfusion.com/downloads/support/directtrac/general/ze/SfDashboardWASM-210347961.zip
KB link (NuGet clean in Visual Studio applications) : https://www.syncfusion.com/kb/6987/how-to-clear-nuget-cache#:~:text=Command%20Line%20Interface.-,Using%20Visual%20Studio,is%20cleared%2C%20click%20ok%20button.
Please check the shared sample and get back to us if you need any further assistance.
Regards,
Leo Lavanya Dhanaraj