I am having trouble with column filters after upgrading to 17.2. We upgraded from 16.1. We are on the
Attached are two samples. These need to be introduced into the 17.2 samples browser to see what I'm talking about.
The one that is called "BindingDataTable" is basically the scenario we were using, and it no longer works. We are on 17.2 service release 2188.
SamplesModified.zip
If you run that sample, you will see that it fills a table with customers. Please filter the "Customer ID" column by "ALFKI" and then click the Refresh button. You will see that your filter is no longer being applied to the data, even though the visual feedback (in column header) indicates that the filter is still in effect. This is a problem for us because in the prior version of the xamGrid (16.1) the filter seem to behave differently. It remained in effect even after the contents of the ItemsSource data had changed. Please let me know if this is not clear.
Next, please review the "CustomFilterDialog" that is also attached in the zip. You may filter the first name by "arnie" and then click refresh. In this case the filter remains in effect, even as the underlying data has been changed.
Please let me know if there is a reasonable explanation for the change in behavior, or if it is a bug. Ideally the filter would remain in effect, despite underlying changes to the data collection in the viewmodel.
Hello David,
Thank you for contacting Infragistics!
What version of v16.1 are you using? When I test this in v16.1 and v17.2 I get the same behavior.
We are upgrading from 16.1.20161.2231.
When you say "get the same behavior", then which behavior is it? Does the filter remain in effect or does it start being ignored? Please focus on "BindingDataTable" because that is the one that has both behaviors, depending on the version of IG controls.
I'm going to try to upload another sample. This is the full samples browser with some minor customizations. Please use the StartupGrid and tell me what happens when you filter on a customer ID and click the Refresh button
Thank you for the update. When I run in v17.2 2188 and v16.1 2231 I get the same result for binding to the data table. The behavior I see is that I filter the grid so a single row appears, I then click the button to clear and reassign the data. After that the filter is still being applied and I still only see one row of data. I am attaching the sample I made based on the code you have provided.
I don't see an attachment.
I am wondering if you did anything more than me to get this working?
In Process explorer I can select the startupgrid process to see what is loaded. I just see a bunch of uninteresting stuff for the 4.6.2 runtime, along with only four Infragistics assemblies loaded from the GAC (image). It is hard to understand how you are getting a different behavior than I am. I run my workstation on Windows 10 but this is also reproducible on other machines, like Windows 2012 R2 servers we use in production.
Thank you for the update. Here is the sample. Instead of running your sample I created a separate one based on the code you provided as the sample you sent had unnecessary parts for reproducing the issue. So the steps I used were create code using v16.1 then test, upgrade to 17.2 then test again.
1565.XamGrid.zip
Thanks for creating that. That example is demonstrating the desired behavior that I'm going for.
Please modify your XamGrid FilteringSettings to look like the following (using FilterMenu) and compare the behavior of that between 16.1 and 17.2.
Hopefully once you do that, you will begin to see a change in behavior between the two volumes, as we do.
Using "FilterMenu" is the way our application exposes the xamgrid filtering to the users. It is a bit less intimidating than your approach ("FilterRowTop").
Please let me know if "FilterMenu" will change behavior between versions, like it does for us. Thanks for all your time on this.
Thanks,David
PS. I do think your approach ("FilterRowTop") may hold promise as a work-around. Another work-around I'm considering is to downgrad the WPF IG volume from 17.2 to something else. Can you tell me which volume is likely to have introduced this change in behavior, and I will evaluate the preceeding one in order to see if it is suitable for our purposes.
Thank you for the update. When I make this case I see the behavior you describe. I have logged this with the ID 256876 for further investigation. I have also created a private case where I will provide you with more details.
As a note for the workaround I would recommend setting using FilterRowTop as the workaround rather than downgrading versions.