When you use the GridView in custom binding mode, provide the grid with data manually, upon each grid request. The GridView sends requests to the server via callbacks (see Using Callbacks). Each callback type should be associated with a handling Action in a Controller. You can define callback routing logic by using specific properties exposed by the grid. This topic provides information about the available callback routing properties of the GridView and specifies which particular Actions should be handled in custom binding mode.
Callback Routing Properties
In general, the GridView has the following properties that allow you to define callback routing logic for different actions. The table below describes which properties and corresponding Actions relate to the custom binding implementation of the grid.
The GridView automatically updates (re-renders) itself after this custom callback, so it is necessary to provide the grid with data during callback processing.
If the MVCxClientGridView.PerformCallback client method is used in your project, it is essential to handle the specified Action to implement the grid's custom data binding. The specified Action only accepts a parameter passed via the PerformCallback client method. No specific custom binding parameter is automatically passed to the Action.
The GridView does not automatically update (re-render) itself after this custom data callback, so it is not necessary to provide the grid with data during callback processing.
Handling the specified Action is not required to implement the grid's custom data binding. No specific custom binding parameter is automatically passed to the Action.
Action Types and Parameters that are Specific to Custom Binding
The GridViewSettings.CustomBindingRouteValuesCollection property allows you to assign particular handling Actions for four data operations - Paging, Sorting, Grouping and Filtering - which are specifically exposed to be handled in a custom manner to implement custom data binding of the GridView. These operations are identified by values of the GridViewOperationType enumeration. The table below lists the available data operation types, and provides additional information on how to assign and declare Actions that handle these operations.
An operation of this type is initiated if the paging-related state of the grid is changed. For instance, an end-user moves to another grid page (by clicking a pager navigation button or page number button) or changes the grid's page size (using the pager's page size combo box).
An operation of this type is initiated if the sorting-related state of the grid is changed. For instance, an end-user sorts a column by clicking its header.
Note that a regular click on a column header clears the sort settings on other columns. To preserve the existing sort settings of other columns, an end-user can hold the SHIFT key down while clicking. This can be useful when sorting against multiple columns.
An operation of this type is initiated if the grouping-related state of the grid is changed. For instance, an end-user moves a column header to the group panel to group grid data by values of the column.
Represents the current state of the column related to the performed filter operation.
Note: When implementing the grid's custom data binding, the DevExpressEditorsBinder must be used instead of the default model binder to correctly transfer values from DevExpress editors back to the corresponding data model fields. See the Binding to Model section in the Binding Data Editors to Data topic for more details on how to specify DevExpressEditorsBinder as a model binder.
Was this page helpful?
Thanks for your feedback! Any other suggestions? Tell us here.