I am having considerable issues with the Grid Filter functionality, there are a couple of problems.
With the grid setup as below:
with these 2 fields:
With these two fields, the second field attempts to filter using the field name of the first, so the second of these columns PersonnelKey will send a ajax query to the server for filtered data but it uses the wrong field name ClientContactId instead of PersonnelKey
Sometimes the second field column refuses to send any ajax query at all to filter the table.
But oddly if the fields are swapped in source code or at run time with column reordering the behavior changes, then the 1st column filters properly but the second column filters with the other columns field. The second column has the issue, irrespective of which column it is.
If ClientContactID is the first field, the PersonnelKey field has the problem,
If PersonnelKey is the first field, the ClientContactID field has the problem,
and the problem doesn't care if the order is changed via xaml source or by run time reordering.
I have attached the controller, the view, and the lookup object that is being used by ViewBag
Pavithra SubramaniyamSeptember 23, 2019 11:00 AM UTC
Thanks for contacting Syncfusion support.
We have validated the provided information and we already logged “ForeignKey columns filtering is not working properly in remote data with same foreignKey field name” as a bug and the fix included in our Volume 2 SP1 Release so we suggest you to use the latest version(v.17.2.51) to resolve the problem.
If you still face the problem then share the package version details that will helpful for us to validate further at our end.
SLScott LambertSeptember 23, 2019 02:33 PM UTC
Thanks for your prompt reply. I am using the Nuget package Syncfusion.EJ2.AspNet.Core 220.127.116.11. I will change the Foreign Key name hopefully that will correct the issue. I tried the link you gave and I get the following error page.
This private feedback is not associated with your account.
If you believe that this error message is incorrect, please feel free to contact us
Pavithra SubramaniyamSeptember 24, 2019 11:38 AM UTC
Thanks for your update.
We have created a sample with latest version, checked at our end and its working fine. Please refer the below sample for more information.