The GridTableView object has an Items property that contains all the data rows in the table view. Each row is represented by a GridDataItem or GridEditFormItem object, depending on whether the row is an edit form. The GridDataItem or GridEditFormItem has an ItemIndex property that is its index in the Items property collection.
When implementing an event handler for an event such as ItemCreated,
UpdateCommand, InsertCommand or DeleteCommand, you can obtain a GridDataItem or GridEditFormItem for the row from the event arguments (e.Item or, in a hierarchical grid, e.Item.OwnerTableView.ParentItem).
Accessing Cells Using Column Unique Name
Because of features such as column reordering and grouping, the index of individual columns can change on the client. This means that using indexes to access individual cells in the Cells collection of a row is not a reliable method of obtaining a cell in a particular column.
To provide a reliable way of locating the cell in a particular column,
each column in the grid has a UniqueName property
of type string. This property is assigned automatically at design time. For example,
an auto-generated GridBoundColumn with DataField
'ContactName' generates a UniqueName of 'ContactName').
You can also set the UniqueName property explicitly, although
the automatic generation handles most cases. Using the UniqueName property
of a column lets you reliably locate a column even when its index changes.
To get the cell's value, use the Text property of the cell:
This approach of obtaining cell values works for auto-generated columns and built-in column
types except for template columns. For template columns, you must find the control in the grid cell and extract its value.
The same approach can be applied to header and footer items. Simply reference the header or footer item of the control and use the column UniqueName property to identify the cell of interest:
Accessing Controls in Template Column
While accessing cells with Template columns remains the same, you could use a little different approach to get the controls in the cell.
For example, to access a TextBox declared in the ItemTemplate of the column:
Accessing the Value of Cells in Edit Mode
If the grid item is in edit mode, you can still use the column's
UniqueName to access the cell (even if it is in an edit form).
Then you can locate the control that contains the cell's value and,
depending on the
type of the column editor, cast it to the appropriate type, and access the value.
If you have a reference to the column object, you can get an instance of
GridEditManager from the item and use its
GetColumnEditor(editableCol) method to access the column editor.
For a live example that uses GridEditManager to access the column editor, see Using Column Editors.
Accessing Controls in Edit/Insert Mode
When editing or inserting a grid item, you could access and modify the controls generated
in the editable item.
However, you will need to use a different approach corresponding to the chosen
InPlace EditMode is supported only for an AutoGenerated
EditFormType. In this case, the editable item is of type GridDataItem or GridDataInsertItem,
rather than GridEditFormItem and GridEditFormInsertItem as usual.
Accessing Cells in Client-Side Code
Accessing Table Views in a Hierarchical Grid
In a hierarchical grid, each item in the Items collection of a parent GridTableView has a ChildItem property of type GridNestedViewItem. This child item is the container for the nested child table(s). The GridNestedViewItem has a NestedTableViews property that holds the collection of all the detail tables for the parent table.
You can use these properties to access the detail tables of a row in the parent table, as follows:
Conversely, if you have a reference to the instance of an item in a child table and want to access the parent table view, you can use the ParentItem property.