I searched the web on this topic and got plenty of suggestions from every one (including other stackoverflow threads).
Finally, I thought implement as shown exactly here.
http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.repeater.onitemcommand(VS.71).aspx
Still frustrated.
My repeater is available in a user control and I added the user control as a web part to an existing webpartzone. I could see all rows in the repeater (along with buttons). Once I click the (any) button, it loses all the rows and itemcommand never fires.
I am using ASP.NET 4.0
Can anyone help me on this.
Databound list controls (just like any other dynamically-created controls) need to be recreated on postback. Do you have your Databind call within an if (!IsPostback) {} ?
Source code might help determine your specific issue.
All the time, the Repeater has to be bound. Otherwise, Repeater_ItemCommand EVENT of the Repeater won't be fired.
That means:
if (!IsPostBack)
{
BindRepeater();
}
else
{
BindRepeater();
}
Related
I can´t find anything like onrowclick or onclick event, is possible to fire event when you click on gridview row?
Not using standard ASP.NET control events, since one does not exist for that purpose. Instead, you could use client-side JavaScript to issue an AJAX request, exposing a static WebMethod to handle the thing: but, without knowing why, this might be absolutely useless.
do this in grid RowDataBound event:
if(e.Row.RowType == DataControlRowType.DataRow)
{
e.Row.Attributes["onClick"] = "";//any thing you want.
}
I have a TextBox inside an UpdatePanel which is inside of a GridView. The purpose of the UpdatePanel is to update the TextBox when the TextChanged event is called (like in a previous question of mine).
This i got working after I read into the topic. But the problem I am stuck with now is that I have to add new data to the GridView at PostBack and the following new rows don't fire the TextChanged event. Only the first row in the GridView does.
Therefore I thought of setting the EventHandler for the TextChanged event in the RowCreated event so the Handler is set before the new rows are created but I still seem to miss something here. Any clues will be gladly taken :)
PS: If you want to see some of my code I have to refer for now to the code from the previous question as I am currently at home. I can post it as soon as I get back to work tomorrow.
Stupid me strikes again!
In codebehind the AsyncPostback never got to the part where the gridview built the new rows at postback. Therefore the TextChanged Event only occured for the first row since it is the only row which is also built when no postback is occuring.
The tricky part here is to find out in AsyncPostback if the last time Page_Load was called through PostBack or not. I think I solved it through a very dirty way: on PostBack I wrote in Page_Load to a hiddenField a certain value. Afterwards I checked if the value is still in the hiddenField. If so, then I knew that in the AsyncPostback I have to go the route of the PostBack and if not then not.
If somebody comes up with a better way to achieve this you are welcome to enlighten me :)
I'm using a datapager control on my listview to perform paging in it.
When paging through the table, I need to perform some validations. When these validations are not successfull, the paging should be cancelled.
I currently perform the validation in the PagePropertiesChanging event of the ListView, however, the arguments do not provide a Cancel property.
protected void MyListView_PagePropertiesChanging(object sender, PagePropertiesChangingEventArgs e)
{
if (!Validate())
{ // cancel the paging action}
}
Does anyone know if canceling the paging is possible and how to perform it?
Thanks
I too was disappointed to find there was no simpler way to do this. I ended up very much like Littlefool, where I made use of the PagePropertiesChanging event. In it, if my validation did not pass, I called the SetPageProperties() on my DataPager with a saved off value of its previous StartRowIndex value, which I save off in the ViewState.
Not my proudest solution but it works.
Could you not simply manually page?
Eg Validate then page if OK, as opposed to try and page, validate, then cancel.
Hi I have a Repeater and I am doing various things during the ItemDataBound event. My Repeater is in a control. What I am noticing is that the things that are supposed to happen in the ItemDataBound event happen after the Page_Load of the page hosting the control. Is there a way to use some sort of ItemDataBoundComplete trigger so I can do other things on my page after the events of the ItemDataBound have taken place? Thanks, please let me know if I have not been clear.
[Edit] I have controls that are being bound to the ItemDataBound and they are not available until after the Page_Load for the page hosting the control.
[Solution] (In my case):
In my page I used the following:
Control.Page.LoadComplete += new EventHandler(Control_LoadComplete);
Then I performed what I had to do in that event.
What kind of things? You can override the OnPreRenderComplete method, which is called immediately before the page renders.
You can also change to a ListView, which is support as much flexibility in the html, and use the DataBound event (which is called after the whole ListView has finished data binding).
My understanding of the order of page events is this:
Page : Load
Control : DataBind (for a GridView or whatever)
Control : Load
Control : Clicked (for a Button)
Page: PreRender
Control : PreRender
(There are lots of others - but these are the ones I'm interested in)
The important thing to notice here is that the button's click event comes after the gridview's bind event. If the button causes a change to the data, the GridView displays the old data. I could rebind the control in the PreRender event, but that seems totally ugly.
This must be a very common pattern (a button that updates data). How do I put this together so that the GridView binds to the data after the Button click changes it?
The answer was in the Button Click event, after the data has been changed, call DataBind() on the page to cause the GridView (and anything else that needs it) to rebind. I didn't realise you could do that.
Thank you Ocdecio & Mufasa - I would mark your answers as helpful, but I got no rep yet.
ASP.NET does, by default, lots of binding and rebinding. Rebinding after a click event is normal.
The only reason the button click event comes after GridView bind is because you programmed your page to do that . I don't see any problem in binding the control in the PreRender event, in fact that is the only way to take action after a control event (such as Button onclick).