Modifying Data Using a DetailsView Web Server Control

The DetailsView control has built-in functionality for allowing users to edit or delete records without requiring programming. You can customize the editing functionality of the DetailsView control using events and templates.

You can enable the built-in editing functionality of the DetailsView control by setting one or more of the AutoGenerateEditButton, AutoGenerateInsertButton, and AutoGenerateDeleteButton properties to true. The DetailsView control will automatically add the functionality to allow users to edit or delete the current bound record and to insert a new record, provided the data source for the DetailsView control supports edits.

The DetailsView control provides a user interface (UI) that allows users to modify the contents of a bound record. Typically, an editable view displays an additional row that contains command buttons with the text Edit, Insert, and Delete. By default, the row is added to the bottom of the DetailsView control.

When the user clicks a command button, the DetailsView control redisplays the row with controls that allow users to modify the contents of the row. The edit button is replaced with buttons that allow the user to save changes or cancel editing a row. The DetailsView control uses text boxes to display data in a BoundField and for data displayed automatically when the AutoGenerateRows property is set to true. Boolean data is displayed using check boxes. You can customize the input control displayed in edit mode by using a TemplateField. For more information, see Creating a Custom Row in a DetailsView Web Server Control.

When the DetailsView control is performing an insert operation, it passes the values to be inserted in the data source using the Values dictionary collection.

For an update or delete operation, the DetailsView control passes values to the data source in three dictionary collections: the Keys dictionary, the NewValues dictionary, and the OldValues dictionary. You can access each dictionary using the event arguments passed to the insert, update, or delete events raised by the DetailsView control.

The Keys dictionary contains the names and values of fields that uniquely identify the record to update or delete, and always contains the original values of the key fields before the record was edited. To specify which fields are placed in the Keys dictionary, set the DataKeyNames property to a comma-separated list of field names that represent the primary key of your data. The Keys collection is automatically populated with the values associated with the fields specified for the DataKeyNames property.

Note Note

The original primary key values for the fields specified in the DataKeyNames property are stored in view state. If your primary key values contain sensitive information, you should encrypt the view state contents by setting the page's ViewStateEncryptionMode property to Always.

The Values and NewValues dictionaries contain the current values from the input controls in the record being inserted or edited, respectively. The OldValues dictionary contains any original values of fields except the key fields, which are included in the Keys dictionary. New values for key fields are included in the NewValues dictionary.

The data source control uses the values from the Keys, Values, NewValues, and OldValues dictionaries as parameters for its insert, update, or delete command. For information on how data source control parameters are created based on the dictionaries created for bound values, see Using Parameters with Data Source Controls for Inserting and Updating.

After an update, the DetailsView control raises its ItemUpdated event. This event allows you to perform post-update logic, such as integrity checks. Similarly, the DetailsView control raises its ItemInserted event after an insert and its ItemDeleted event after a delete.

After the update is complete and all events have been raised, the DetailsView control rebinds to the data source control to display the updated data.

By default, the DetailsView control automatically generates a row for each bound field from the data source. You can customize which fields are bound to the DetailsView control by setting the AutoGenerateRows property to false and specifying a BoundField control for each field that you want displayed in the DetailsView control.

To customize how command buttons are displayed, you can set the DetailsView control's AutoGenerateEditButton property to false. You can then add individual CommandField objects for a row. For example, to place the current displayed row into edit mode, you can add a CommandField field with the ShowEditButton property set to true.

You can specify whether a bound field is editable using the ReadOnly property of the BoundField control. When the ReadOnly property is set to false, the field will be editable when the user clicks the Edit command button. When the ReadOnly property is true, the bound field will be displayed, but the user will not be able to edit the field.

Similarly, you can specify whether a value can be inserted for a bound field using the InsertVisible property of the BoundField control. If the InsertVisible property is false, then the bound field will not be displayed when the user clicks the New command button. This is especially useful when the bound field is automatically generated by the data source, such as a date and time stamp or an auto-incrementing primary key.

The following code example uses a GridView control and a DetailsView control to display data. The DetailsView control is configured to allow the data to be modified.

<%@ Page language="C#" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
<script runat="server">

  void EmployeesDropDownList_OnSelectedIndexChanged(Object sender, EventArgs e)

  void EmployeeDetailsView_ItemUpdated(Object sender, DetailsViewUpdatedEventArgs e)
    EmployeesDropDownList.SelectedValue = e.Keys["EmployeeID"].ToString();

  void EmployeeDetailsView_ItemDeleted(Object sender, DetailsViewDeletedEventArgs e)

  void EmployeeDetailsSqlDataSource_OnInserted(Object sender, SqlDataSourceStatusEventArgs e)
    System.Data.Common.DbCommand command = e.Command;   
    EmployeesDropDownList.SelectedValue = 


<html xmlns="" >
  <head runat="server">
    <title>Northwind Employees</title>
    <form id="form1" runat="server">

      <h3>Northwind Employees</h3>

        <table cellspacing="10">

            <td valign="top">
              <asp:DropDownList ID="EmployeesDropDownList" 
                RunAt="Server" />            

            <td valign="top">                
              <asp:DetailsView ID="EmployeeDetailsView"

                <HeaderStyle backcolor="Navy"

                <RowStyle backcolor="White"/>

                <AlternatingRowStyle backcolor="LightGray"/>

                <EditRowStyle backcolor="LightCyan"/>

                  <asp:BoundField DataField="EmployeeID" HeaderText="Employee ID" InsertVisible="False" ReadOnly="true"/>                    
                  <asp:BoundField DataField="FirstName"  HeaderText="First Name"/>
                  <asp:BoundField DataField="LastName"   HeaderText="Last Name"/>                    
                  <asp:BoundField DataField="Address"    HeaderText="Address"/>                    
                  <asp:BoundField DataField="City"       HeaderText="City"/>                        
                  <asp:BoundField DataField="Region"     HeaderText="Region"/>
                  <asp:BoundField DataField="PostalCode" HeaderText="Postal Code"/>                    

        <asp:SqlDataSource ID="EmployeesSqlDataSource"  
          SelectCommand="SELECT EmployeeID, LastName + ', ' + FirstName AS FullName FROM Employees" 
          Connectionstring="<%$ ConnectionStrings:NorthwindConnection %>" 

        <asp:SqlDataSource ID="EmployeeDetailsSqlDataSource" 
          SelectCommand="SELECT EmployeeID, LastName, FirstName, Address, City, Region, PostalCode
                         FROM Employees WHERE EmployeeID = @EmpID"

          InsertCommand="INSERT INTO Employees(LastName, FirstName, Address, City, Region, PostalCode)
                         VALUES (@LastName, @FirstName, @Address, @City, @Region, @PostalCode); 
                         SELECT @EmpID = SCOPE_IDENTITY()"

          UpdateCommand="UPDATE Employees SET LastName=@LastName, FirstName=@FirstName, Address=@Address,
                           City=@City, Region=@Region, PostalCode=@PostalCode
                         WHERE EmployeeID=@EmployeeID"

          DeleteCommand="DELETE Employees WHERE EmployeeID=@EmployeeID"

          ConnectionString="<%$ ConnectionStrings:NorthwindConnection %>"

            <asp:ControlParameter ControlID="EmployeesDropDownList" PropertyName="SelectedValue"
                                  Name="EmpID" Type="Int32" DefaultValue="0" />

            <asp:Parameter Name="LastName"   Type="String" />
            <asp:Parameter Name="FirstName"  Type="String" />
            <asp:Parameter Name="Address"    Type="String" />
            <asp:Parameter Name="City"       Type="String" />
            <asp:Parameter Name="Region"     Type="String" />
            <asp:Parameter Name="PostalCode" Type="String" />
            <asp:Parameter Name="EmpID" Direction="Output" Type="Int32" DefaultValue="0" />

            <asp:Parameter Name="LastName"   Type="String" />
            <asp:Parameter Name="FirstName"  Type="String" />
            <asp:Parameter Name="Address"    Type="String" />
            <asp:Parameter Name="City"       Type="String" />
            <asp:Parameter Name="Region"     Type="String" />
            <asp:Parameter Name="PostalCode" Type="String" />
            <asp:Parameter Name="EmployeeID" Type="Int32" DefaultValue="0" />

            <asp:Parameter Name="EmployeeID" Type="Int32" DefaultValue="0" />