GridEvents OnActionBegin causes reload of components

[Alejandro]

In NET 6 (this does not happen in NET5), when we use GridEvents and OnActionBegin, any action causes the reload of the components or the entire page

Attachment: captura_5a8ff361.zip

[Vignesh Natarajan]

Hi Alejandro, 

 

Thanks for contacting Syncfusion support.  

 

Query: “In NET 6 (this does not happen in NET5), when we use GridEvents and OnActionBegin, any action causes the reload of the components or the entire page” 

 

We have analyzed the reported issue with provided video demonstration and prepared a sample as per your suggestion with OnActionBegin event along with .Net 6.0 and latest version Syncfusion Blazor NuGet package. We are not able to reproduce the reported issue at our end when trying to perform search operation in Grid.  

 

Kindly refer the sample below for your reference. 

 

Sample: https://www.syncfusion.com/downloads/support/forum/171221/ze/BlazorGrid_Server-258800801.zip 

 

Kindly share the following details to validate the reported issue further at our end.  

 

1. Share the Grid code example along with actions performed in OnActionBegin event.    
2. Are you facing any script error in browser console. if yes share the screenshot of the issue.  
3. Share your Syncfusion NuGet package version details.
4. Also share the details about your Blazor Application (Server / Client/ Hosted).
5. If possible try to reproduce the reported issue in provided sample and revert back to us.

 

Above requested details will be very helpful for us to validate the reported query at our end and provide solution as early as possible. 

 

Regards, 

Vignesh Natarajan  

[Alejandro]

Thank you very much for the sample. I've done some more research and and seen that it happens when we use an asynchronous CustomPolicyProvider. I attatch your sample modified.

Thanks again

Attachment: BlazorGrid_Server_CustomPolicyProvider_7ce60370.zip

[Vignesh Natarajan]

Hi Alejandro,  

Thanks for the update. 

We are able to reproduce the reported issue in the provided sample and currently we are validating the reported query. We need some more time to analyze the issue. So we will update you the further details in two business days (21^st December 2021).  

We appreciate your patience until then.  

Regards, 

Vignesh Natarajan 

[Vignesh Natarajan]

Hi Alejandro,  

Sorry for the inconvenience caused. 

We are facing some difficulties in validating the reported issue at our end. We need some more time to validate the issue to proceed further. So we will validate and update you the further details by 23^rd December 2021. 

We appreciate your patience until then.  

Regards, 

Vignesh Natarajan 

  

[Vignesh Natarajan]

Hi Alejandro,  

We regret for the inconvenience caused.  

On further validation we found that Grid component gets destroyed (disposed) and refreshed while performing an action in Grid with custom policy and GridEvents. We are validating the reported query further at our end with default callback event. We need some more time to validate the query at our end.  

So we will update you the further details by 30^th December 2021.  

Regards, 

Vignesh Natarajan 

[Vignesh Natarajan]

Hi Alejandro,  

Thanks for the patience.  

We have validated the reported issue with default Blazor components with parent child relation and invoked an EventCallBack function of Child component. We are able to reproduce the similar issue with the Blazor components also. This issue is not related to Grid Component. It is a Blazor Framework issue in DotNet 6. 

We have attached two samples (i.e. in DotNet 5 and Dotnet 6) with same configuration. 

.NET 6: https://www.syncfusion.com/downloads/support/forum/171221/ze/BlazorGrid_CustomPolicy-567939613.zip 

.NET 5: https://www.syncfusion.com/downloads/support/forum/171221/ze/CustomPolicy_Dot51291896233.zip  

In .NET6 sample, kindly refer Counter.razor page where we have defined the components with Parent and Child components. We have displayed text message in Parent component and we have tried to update the text message in Child component EventCallBack function. At that time, component is disposed and refreshed. We have developed each cell in the Grid component as a separate with child content since we have provided support for cell level customization. Same issue does not occur in DotNet 5 application with similar configuration.  

Hence the reported issue is related to Blazor Framework not Grid component. Please get back to us if you have further queries.  

Regards, 

Vignesh Natarajan