And moreover gong by the sequence number makes more sense to me.
Invoking the Rebind() method from postback event handler of outside control or Rad Grid will -not- raise the Need Data Source event.
When the app was running, I edited a value (contact name), then clicked the update button, the (why I raised this issue) mmm…. Is it possible that by some reason you disabled the viewstate for your grid instance? P Hi- I ran into somewhat of the same issue, I was setting up a grid in a control used in another control.
Do you want me to send you the demo app that you gave me re-configured for this environment. Best regards, Stephen the Telerik team Hi Stephen I have manged to get th update click to work along with the correct order of events (but unfortunatly I do not know why) I have moved the placeholder where my (dynamic grid resides) from one part of the page to another location.
This is a strong evidence of such a possible exception.NET is smart enough to do it for me automatically !! Supplement information: Upon clicking Edit Item Template's update link button: Item Command event is triggered, then return and goes no further. This is my foresaid work around solution: programmatically fill in datasource's parameters, when apparently ASP. However, I am still appreciate if anyone can explain this problem.Why isn't Form View's Item Updating event fired, when obviously link button's command name = "Update"? protected void Form View1_Item Command(object sender, Form View Command Event Args e) protected void Object Data Source1_Updating(object sender, Object Data Source Method Event Args e) protected void Object Data Source1_Inserting(object sender, Object Data Source Method Event Args e) private void set ODSParameter(Object Data Source Method Event Args e) Thanks for your suggestion, but I don't think it is a common practice to invoke ODS' update event manually.How to rebind the grid in this case you can learn fromthis help article.The issue occurs when installing the Enterprise Portal on a claims web application, so actually you will also face the same the issue on Share Point 2010 when using claims.