Sorry I should have explained that I still need the column for a hidden filter and therefore cant remove it, just want to hide it...

Hi Devin,

I just assumed that filtering would be faster if the user is modifying the visible list frequently.

However if you guys are using LINQ behind the scenes for the filter anyway it seems to make the most sense.

Am I correct on this point - that you are using LINQ to do the filtering?
Is this also why filtering is quite slow in the grid when lots of unique values (about 900 rows in this grid)?

Regards,
Doug

Yes, we are simply using LINQ behind the scenes to filter the data.

You should not be experiencing any performance problems filtering 900 rows, especially if you are only filtering a simple boolean column.  I've attached a sample XAML page and code file for a sample I wrote that filters a boolean property exposed from a collection of 900 objects and did not experience any perf problems. 

If your experiencing perf issues, I'd be happy to dig into that with you further.

Devin

Hi Devin,

No it isnt the boolean filter that is concerning me performance wise. It is our other string based columns. If I use the UI to add a filter to a column like our Color Description column which probably has around 200 possible values and deselect all but one or two, applying the filter takes several seconds. Also, clearing the same filter takes quite some time and the CPU goes to 50% for an extended period for IE.

However looking at your official samples I can see the one with a million rows (or whatever large number it is) filters very quickly. So I need to investigate some more.

Regards,
Doug

Doug, 

This update is to let you know that I submitted a feature request for the ability to exclude columns from the column chooser.  I have sent you specific information about that request in a private support case.

Thanks,
Francis 

Currently this feature has not been implemened yet.

Hi,

is this feature available yet?