The WebDataGrid™ control’s many behaviors have both server-side and client-side events. These events have the suffix "ing" or "ed" appended to them reflecting the order in which they occur. Depending on the behavior, there are usually two events on each side: an "ing" and an "ed" event.
For example, the EditingCore behavior has a RowUpdating and a RowUpdated event on both the server and client.
The order in which these events get triggered depends on what is happening in WebDataGrid; however, there is a basic order to follow: “ing” events will occur before “ed” events, usually in the order of client to server and back to client.
For example, when updating WebDataGrid with AJAX enabled, moving off a row to trigger the update results in the following order of events:
Client-side RowUpdating
Server-side RowUpdating
Server-side RowUpdated
Client-side RowUpdated
This ordering of events allows you to do any type of custom operation before an event occurs on the client. It gives you another chance on the server if necessary. Then, you can do any type of operations after an event has occurred on the server or client.