Hallo Infragistics Team,
The grid only filters rows on the current page, all pages are still referencable with the paging control but empty, rows on other pages than the current, that should be visible according to the filter are invisible. We upgrade to new Versions regurarily, current Version is 13.2.20132.2094, I cannot remember having these problems before. Our application is in production and we were always satisfied with the filtering. Is there a workaround? Can we go to a former version? I could only find old posts to this subject. Confusing. Please help.
Thomas
Hi Thomas,
I tested the scenario you're describing with the exact build of the control but was not able to reproduce it. Find the attached sample that I used to test this out and probably modify it so this behavior could be reproduced or if it's easier for you provide a sample of your own were the issue is easily observable.
Regards,
Hallo Konstantin, thank you for providing me a sample. I changed it to meet our application structure with MVVM. It is the PagedCollectionView binded to the Itemssource of the grid. We use the PagedCollectionView to control custom filtering in the ViewModel and we use it in quite a few places in the application. I changed back to Version 12.2.20122.2283 and it did not work there eighter. I am quite sure that the PagedCollectionView is/was fully supported by your controls. Our application is in production and my plan is to go back to a version, that works with a PagedCollectionView, unless you tell me that it will be solved in the next release soon. Unfortunatly I must find the proper Version. Can you provide me with a former Version, that fully supports the PagedCollectionView? Regards, Thomas
... the advantage of the PageCollectionView is to easily implement a custom filter/sorting to the binded list. In the provided sample i demonstrated the use of the PagedCollectionView by adding a filter in the ViewModel. Is there an alternative to the PagedCollectionView/ICollectionView for your controls, so that i can easily integrate custom filtering and sorting in the ViewModel? With only List/ObservableCollection it gets rather complicated. And as i said, according to the documentation the PagedCollectionView/ICollectionView should be supported by your controls, at least it was.
thanks for the clarifications. XamGrid should supports PagedCollectionView/ICollectionView and its probably an issue we've introduced. I don't think there is an alternative of ICollecitonView that could let you easily to control the filtering/paging through your VM. I'm about to investigate the provided sample and get back to you shortly. If it turns out it's an regression issue I'll try to find the last release where the issue is not reproducible so you could fix you're application asap. The next SR release projected date is about mid/end of July so it'll probably be too late for you.
Hi again,
I've tested your sample with few versions back(11.1 was the earliest one) and got the same behavior from all of them. After some more research on this it turned out that XamGrid is getting total items count from the PagedCollectionView and the pager control is basically using the collection specific properties. What happens when you filter through the UI of the xamGrid the grid is basically filtering out the items that are supposed to be on the some of the pages and they left empty. The issue comes down to that that the grid uses the info about the paging from the PagedCollectionView, which does not know about the filtering the grid is doing.
So one possible solution is to get rid of the PagedCollectionView and use any other kind of collection that is NOT implementing IPagedCollectionView. Then the grid will handle the paging itself and will be aware of the filters applied, but this way you'll loose the ability to control the paging through your view model.
Another way around this issue could be to hook up to the XamGrids OnFiltering event analyze the filters applied through the XamGrid UI accessible through the event arguments and update the collections Filter predicate so the collection. It would be hard to be implemented so it covers all of the XamGrid's filtering capabilities so this might be more like a hot fix for your app.
Sorry for not being able to provide good enough solution for your case. I could submit an internal development issue on your behalf. Or you could submit a product idea at http://ideas.infragistics.com/forums/192363-wpf .