ASP.NET Tip: Use the ItemDataBound Event of a Repeater

My previous ASP.NET tip, “Responding to the Repeater Control’s ItemCommand Event“, explained how to use a Repeater to respond to events generated within the Repeater. This tip demonstrates how to work with the fields and data within the Repeater.

Each time a data record is added to the Repeater control, an ItemDataBound event is fired. Within the event, you can access the controls that are created, as well as the data being bound to the row. This feature enables you to do a variety of things, such as change the data going in, add attributes to controls, and so forth. This example adds a JavaScript confirmation to the Delete LinkButton control.

The following Repeater control is typical of my own applications:

<asp:Repeater ID="rptData" Runat="server">
   <HeaderTemplate>
      <p class="text"><b>Actions:</b>
      <asp:LinkButton ID="btnAdd" Runat="server"
                      CssClass="text"
                      CommandName="add">Add New Record
      </asp:LinkButton></p>
      <table cellpadding="4" cellspacing="0" width="100%">
      <tr class="tableheading">
         <td width="80%">Name</td>
         <td width="20%">Actions</td>
      </tr>
   </HeaderTemplate>
   <ItemTemplate>
      <tr class="tabletext">
         <td class="tabletext"><%# Eval("Name") %></td>
         <td align="center" class="tabletext">
         <asp:LinkButton ID="btnEdit" Runat="server"
                         CssClass="tabletext" CommandName="edit"
                         CommandArgument='<%# Eval("pkRecordID")
                         %>'>Edit</asp:LinkButton>
         |
         <asp:LinkButton ID="btnDelete" Runat="server"
                         CssClass="tabletext" CommandName="delete"
                         CommandArgument='<%# Eval("pkRecordID")
                         %>'>Delete</asp:LinkButton></td>
      </tr>
   </ItemTemplate>
   <AlternatingItemTemplate>
      <tr class="tabletext_gray">
         <td class="tabletext"><%# Eval("Name") %></td>
         <td align="center" class="tabletext">
         <asp:LinkButton ID="btnEdit" Runat="server"
                         CssClass="tabletext" CommandName="edit"
                         CommandArgument='<%# Eval("pkRecordID")
                         %>'>Edit</asp:LinkButton>
         |
         <asp:LinkButton ID="btnDelete" Runat="server"
                         CssClass="tabletext" CommandName="delete"
                         CommandArgument='<%# Eval("pkRecordID")
                         %>'>Delete</asp:LinkButton></td>
      </tr>
   </AlternatingItemTemplate>
   <FooterTemplate>
   </table>
   </FooterTemplate>
</asp:Repeater>

The first thing to do is to register for ItemDataBound events on your repeater control, which I prefer to do in the OnInit event of the page. Here’s the code to do that:

override protected void OnInit(EventArgs e)
{
   base.OnInit(e);
   rptData.ItemDataBound +=
       new RepeaterItemEventHandler(rptData_ItemDataBound);
}

private void rptData_ItemDataBound(object source,
                                   RepeaterCommandEventArgs e)
{

}

Each item will generate an ItemDataBound event, but you will also get events for other types of items, including the header and footer. As a result, you need to protect your code by checking the ItemType before trying to do any work. The following code adds the confirmation dialog:

private void rptData_ItemDataBound(object source,
                                   RepeaterCommandEventArgs e)
{
   if (e.Item.ItemType != ListItemType.Item && e.Item.ItemType !=
      ListItemType.AlternatingItem)
      return;

   LinkButton btn = (LinkButton)e.Item.FindControl("btnDelete");
   btn.Attributes.Add("onclick", "if
      ( ! confirm( 'Delete this record?' )) return false; ");

}

This code looks for Item or AlternatingItem rows, finds the btnDelete control using the FindControl method, and then adds the onclick attribute to the Attributes collection. The result is that when the user clicks the Delete LinkButton, an OK/Cancel dialog pops up to confirm the delete. This is a handy way to protect the user from doing something dangerous.

About the Author

Eric Smith is the owner of Northstar Computer Systems, a Web-hosting company based in Indianapolis, Indiana. He is also a MCT and MCSD who has been developing with .NET since 2001. In addition, he has written or contributed to 12 books covering .NET, ASP, and Visual Basic.

More by Author

Get the Free Newsletter!

Subscribe to Developer Insider for top news, trends & analysis

Must Read