ASP.NET MVC Controls

ComponentOne's MVC Edition CollectionView is a service that implements the ICollectionView interface to display data in data-bound controls, such as FlexGrid. CollectionView is a very powerful concept since it provides a layer that wraps the actual data and performs various operations like sorting, filtering, grouping etc. without affecting the actual data. In simple terms, you can think it as DefaultView of the datatable.

The CollectionView class has the capability of keeping a track of changes made to the data and managing the current record. You can manage editing, adding, and removing items, paging etc. It implements INotifyCollectionChanged Interface which notifies listeners of dynamic changes, such as when an item is added and removed or when the collection is sorted, filtered, or grouped.

The CollectionView class implements the following interfaces:

CollectionView supports Server-Side and Client-Side operations.

Server-Side Operations

The server side CollectionViewHelper is a service that enables collections to have reading, editing, filtering, grouping and sorting ability, this is similar to .Net ICollectionView. On the server, CollectionView internally handles sorting, paging, filtering requests by data bound controls. This section describes how to use Create, Read, Update, Delete and BatchEdit actions for CRUD operations:

Client-Side Operations

CollectionView has a powerful client API. CollectionViewHelper internally performs server side operations like sorting, filtering, paging on data for data-bound controls like FlexGrid, FlexChart and other Input controls. However it is possible to explicitly perform these operations on client-side too. The Client-side operations include Current Record Management, Sorting, Filtering, Grouping and Tracking Changes.

See Wijmo CollectionView API Documentation for more information on CollectionView's client-side API.



Copyright © GrapeCity, inc. All rights reserved.

Product Support Forum |  Documentation Feedback