These features are provided out-of-the-box and are not configurable by programmers.Or, at least, not declaratively and, maybe, not easily.The default set of data fields includes templated, image checkboxes, and hyperlink fields.
However, to make use of the Details View control's advanced capabilities you must explicitly declare the row fields to include in the Details View control. The row fields specified are added to the Details View. Note: Explicitly declared row fields can be displayed in combination with automatically generated row fields.
Automatically generating the rows provides a quick and easy way to display every field in the record. Fields collection allows you to programmatically manage the row fields in the Details View control.
It s fairly common for Web applications to work on a single record at a time.
For example, displaying the contents of a single record of data is a necessary practice when you build master/detail views. NET 2.0, the Details View control renders a single record at a time from its associated data source, optionally providing paging buttons to navigate between records and Create/Read/Update/Delete (CRUD) capabilities.
Next, you can use a Grid View control on another, or the same, page to retrieve any just-inserted records.
As you can see in Figure 1, input fields are empty and don t suggest any values to users.
The Details View control can be bound to a data source control (such as the Sql Data Source control or Object Data Source control) or to any data source collection that implements the IEnumerable interface, such as Data View, Array List, List`1, or other collection types.
To declare the row fields, first set the Details View. When both are used, explicitly declared row fields are rendered first, followed by the automatically generated row fields.
The table in Figure 2 details the supported events. It is interesting to note that the Item Command event doesn t fire if the user clicks on the Edit or Insert buttons or any other standard buttons.