I'm not sure which posts you are referring to but I suspect that they were referring to a different type of filtering. ICollectionView (which is a WPF framework interface) provides a means to use a predicate to filter the data source. There is no ui to it, its just a programatic way that WPF provides to filter the collection. There were issues at one point that when bound to a collectionview that had filtering that the grid may show all of the data anyway but that was addressed a while back. This functionality of being able to filter the collection view is supported in the Express and Full versions of the product.

The other type of filtering is a custom filtering usually referred to as record filtering that was added to the datapresenter controls in 9.1. When enabled the control will either show a filter record where you may type in the filter criteria or an icon in the field labelpresenter that when clicked would present the end user with a list of values (and some special filters) that they could use to provide the filter criteria. The grid would then filter its list of records based on this information (these filtered records could be hidden, disabled or you could alternatively style these records to appear differently in the ui). This functionality is not available in the Express version.

With regards to the xamDataGrid being free that is not entirely accurate - the Express version of the controls (which includes an Express version of the xamDataGrid) is free to use. Note that does not mean that the Express version of the xamDataGrid includes all of the functionality of the Full version of the xamDataGrid. The record filtering and fixed fields functionality added in 9.1 was only added to the Full version of the control. I apologize for any confusion about this.

I'm actually a little confused about this as well.  I've seen multiple posts from Infragistics staff that say that filtering is "Standard" for the xamDataGrid.  There are also claims the xamDataGrid is free for use. 

Can you explain exactly why it's being phrased the two different ways?

Thanks,

-Brandyn

Your blurb about the free download is misleading, as it indicates:

"NetAdvantage for WPF Express gets you started with the xamDataGrid™ for WPF development (this is not a trial and features the real xamDataGrid; no purchase is necessary to use it in your applications)."

Filtering is a pretty darned necessary feature when working with any but the smallest data sets.  I'd surely like to use it.  (Note also that user-reordered fields also aren't available.) I don't need any more than this one control, but at a seat cost of $1000 it isn't even close to reasonable.

I have two asks:

1: Could you post a list of features which are not actually available in the 'Express Version'

2: Would you consider licensing controls individually?  Especially for the smaller developers out there who could benefit from the time savings your packages provide for our less grand (and lower-budget) products.

Thanks.

While the object model includes them, new features like record filtering and fixed fields are not supported in the express version. They are only available in the full version. I'm not sure why you are even able to see the filter record as an exception should have been generated when setting AllowRecordFiltering.