Hi there.
There is a problem with clearing the search control entry by pressing
the X at the right.
After many clicks, finally, it clears.
Th behavior is recorded in the video
here...
Syncfusion version : 19.4.0.48
Thanks for your support.
I would like to report also that sometimes by clicking the (X) symbol, an error is occured :
System.NullReferenceException
HResult=0x80004003
Message=Object reference not set to an instance of an object.
Source=Syncfusion.Blazor
StackTrace:
at Syncfusion.Blazor.Grids.Internal.Filter`1.<RemoveFilterColumnByField>d__89.MoveNext()
Hi there Renjith.
I am very pleased from your immediate response.
Unfortunately the result was disastrous.
I have two grids in the same page, with custom adaptor, retrieving data from an sql server, in paging mode.
With this update, the first grid stopped calling the custom adaptor's ReadAsync.
The second grid calls ReadAsync once, and then it doesn't call it at all on search, so nothing is found allways...
The X symbol, continues not to work.
Turning back to 19.4.0.50 version, functionality resotored as well.
Hi Rigakis,
Query : the first grid stopped calling the custom adaptor's ReadAsync. The second grid calls ReadAsync once, and then it doesn't call it at all on search, so nothing is found allways...
We are not clear about the exact scenario you are facing the reported problem. We checked this scenario by containing two grids in a same page, the ReadAsync methods of corresponding Grids triggers fine with the sample from our side. We are attaching the sample for your reference, please download and refer the sample from the link below,
Sample : https://www.syncfusion.com/downloads/support/directtrac/general/ze/ServerApp1281259848
If you are still facing difficulties then the following details would be helpful for us to proceed further.
The provided information will help us analyze the problem, and provide you a solution as early as possible.
Regards,
Renjith R
Hi there.
After mutch search I found out that you can reproduce the behaviour by just adding an (even empty) onLoad event to the grids of your example.
Everything breaks down after that.
I repear, only in 19.4.0.52
In 19.4.0.50 everything works fine.
The (X) symbol have the same (wrong)behaviour even in
19.4.0.52
Hi Renjith R,
I can confirm this behavior. I think it has nothing to do with missing Ids. I only have one grid. It does not happen to all fields - only on the first one in the video. (Order does not matter). If I clear the filter field manually everything is OK. As soon as I use the X to clear this field the error happens - see attached video.
Version: 19.4.0.52 / Win 10 German / Visual Studio 2022 Community
regards
Uwe
Attachment: Grid_Error_20022022_145000_caa3bcf7.zip
Hi Renjith R,
did some further testing ... Changed
<GridColumn Field=@nameof(KaoaInfo.Sch_FullName) HeaderText="Schüler Name" AutoFit="true"></GridColumn>
to
<GridColumn Field=@nameof(KaoaInfo.SchFullName) HeaderText="Schüler Name" AutoFit="true"></GridColumn>
and the error is gone. Maybe you check into this direction ..
regards
Uwe
Hi there.
I'm sending you a video to confirm the behavior, here...
It’s the code you sent to me.
I’m REMing the second grid. It has nothing to do with it.
When enabling load event (only in 19.4.0.52 version) the control never calls ReadAsync.
The (X) for the searching box is behaving badly in all versions.
Hi there.
The problem with the load event has been corrected!
Thank you.
Waiting for the (X) misbehavior solution.
Unfortunately, the link you gave to me is not working (for me)
Hi there.
I have received an email saying,
"We are
glad to announce that, we have included fix for the “Not able to clear the
filtering using clear icon” in our release(19.4.0.54). " (i Cannot find this reply in here)
Unfortunately, it doesn't work either in this version.
It would also be more user friendly if the x symbol was permanently showing for all search boxes or (even better) for the boxes that have a filter applied.
This way it would not need two clicks for every box to clear it.
Hello there.
Any news for the specific problem?
Hi Rigakis,
Sorry for the inconvenience.
Due to some complexities we could not include the fix for this issue in our latest nuget release. This is expected to be rolled out in our upcoming release planned to be rolled out on April 26, 2022.
Until then we appreciate your patience.
Regards,
Renjith R
This is fixed in latest version 20.1.0.55
Thanx a lot!!!
Hi Rigakis,
Thanks for your update. We are glad to hear that the reported issue is resolved. Please get back to us if you need further assistance.
Regards,
Renjith R