Users can double-click on the far edge of a field so that it resizes to accommodate the width of its content, just like in Microsoft® Excel®. With numerous properties, you can optimize precisely how, where and when field auto-sizing behavior takes place within your application's grid view.

Completely customize the way cells are presented to your users.  We have all seen codes used in data that were meant to be processed by machines -- not people!  By associating your own CellValuePresenter with a xamDataPresenter™ field, you hold the power to present this information in a more usable form, such as converting a number into a picture of that many stars for a consumer rating.

Users can group records by common value in one or more fields, even if the fields are at different levels of your data's hierarchy!  All they have to do is drag the field headers into (or out of) the completely stylable group-by area that we give you on the data presenter.

If your business objects implement .NET's IDataErrorInfo interface, then the data presenter can leverage that implementation so as to provide your users with custom error indicators, and a tooltip with your error message at any of the cell, field and/or record levels.  Your users will see one seamless notification scheme, whether an error was signaled by IDataErrorInfo or by our own checking of value editor validation constraints that you can define for each field.

Just like in Windows® Explorer or Microsoft® Outlook®, your users can now choose from a list of fields to add or remove them from the data presenter's field layout. Let your users decide if they want to work with a simple or detailed view of your data.

In addition to support for Fixed Fields (that is, fields which remain fixed in place so your users can scroll the data presenter horizontally), your users can Fix Records at the top or bottom of the data presenter's GridView.  Both of these features work on a pushpin metaphor that your users will instantly recognize.  Fixed Fields and Fixed Records can be custom styled to distinguish them from non-fixed data that is free to scroll.

Alert your users as record or cell values change by highlighting how that value is presented when the DataValueChanged event fires.  An example is when you want to flash cells because their values have changed.  By default, DataValueChanged will only fire for records visible to the user when you enable this feature on the FieldSettings' DataValueChangedNotificationsActive property, although you can change its scope so that it fires for more records than that.

You can have the data presenter keep a history of value changes for you by setting the FieldSettings' DataValueChangedHistoryLimit property to the number of recent value changes you want retained.  The default history is 1 (the most recent value only), although you can increase it to show users a recent run of up- and down-ticks in value as this example illustrates.  Larger values for DataValueChangedHistoryLimit will require progressively more memory.