The grid will work properly if I stay on the page. If I exit the grid page and go to the home page and come back the paging or grouping may or may not work. It always stops working after switching to the home page twice. It also does this with other pages I have created.
I assume it is my coding or a blazor refresh issue but I do not know how to resolve it. I provided an attachment with a video of what is happening along with the NavMenu.cs, EntityList.cs(SFgrid page) and Home Page.
Thanks for looking at it.
I added a Refresh toolbar button, which refreshes the current page then the pager control stops working.
ie:
if (args.Item.Id.Contains("Refresh")) { //entityGrid?.Refresh(); navigationManager.NavigateTo($"/Entity/{typeEntity}", forceLoad: true); }
Hi Larry,
Greetings from Syncfusion support.
From your query, we prepared simple level sample based on your shared sample,
but we’re unable to reproduce the reported issue at our end. Kindly reproduce
the mentioned issue in the provided sample or share the runnable sample to us,
for further validating the query. Refer the attached sample and video demo for
your reference.
Regards,
Sarvesh
Thank you for looking into this. I am uploading the entire project along with a LDF/Log with a BAk if that is easier.
The only change to the original project I made was to remove the license key from program.cs.
Hi Sarvesh, wondering if you had a chance to load the project. Thanks for your help.
Hi Larry,
Sorry for the delay and inconvenience caused.
We’re facing some complexities while evaluating the shared sample. We’ll validate and provide further details within three business days.
Until then we appreciate your patience.
Kindly get back to us if you have any further queries.
Regards,
Sarvesh
I'm still patience and grateful. I'm hoping the complexities of the sample have been overcome.
Let me know if I can assist you in anyway.
Thanks
Hi Larry,
We apologized for the inconvenience caused. We’re able to replicate the
mentioned issue and tried to figure it out the root cause of an issue by
creating simple sample based on your sample at our end. We’ll prioritize your
query and provide a proper update on March 16th, 2023, without any
excuses and delay. Thank you for your patience and understanding.
Regards,
Sarvesh
Hi Larry,
We apologize for any inconvenience this may have caused and we are committed to
resolving this for you.
Based on our initial evaluation, we believe that the issue may be related to binding data on the OnParameterSetAsync function. This could be causing the problem you are facing. However, to provide you with a detailed solution, we will need to further evaluate the issue.
We will be providing you with a detailed solution to your
query on March 22nd. We appreciate your patience in this matter.
Regards,
Sarvesh
Hi Larry,
Thanks for the patience.
We are able to reproduce the reported issue in your shared sample. On validating further we could see that the issue occurs due to the below highlighted code which is rendered inside SfGrid component. So kindly comment out the below line and check the reported issue at your end. Also we have included the modified sample. Kindly check this for additional information.
<SfSpinner @bind-Visible="@spinnerVisible"> </SfSpinner> |
If the rendered spinner component is necessary then kindly share us the use case or exact requirement so that we will check and update the feasibility in achieving your requirement. Please let us know if you have any concerns.
Regards,
Monisha
Thank you... for resolving the issue. I guess putting a SFSpinner control within the SFGrid control is a bad idea.
Thanks again.
Hi Larry,
We are glad that the provided solution helped to solve the issue.