i have place ultrawebgrid inside updatepanel now on pressing button 1 i am filling it and then i change some of its cell values and press button 2 to save them but when i try to extract those updated values gets old values before updation
can any one guide where is the problem????
I have found this exact issue myself (as a noob in ASP.NET and infragistics)
A simple (elegant) solution is to set the webgrid's data source to a variable of the page (i.e. a class variable of the Page class.
This way, your data source is stored across post backs, even for immediate changes (not requiring a button click).
Generally, you would handle the grid's UpdateRowBatch event in this scenario, which is raised once for every row that was updated since the previous postback. (UpdateRow does the same, except that it triggers a postback immediately when a row is updated.) It's important that you don't re-bind the grid in Page_Load during the postback where updates are being processed, becasue the update events won't work.
I don't understand your project's setup based on the description so far, so it's difficult to provide a more specific descripition. You might consider creating an isolated sample that demonstrates what you have so far, and submit a support request to detail where your sample is falling short of the updating behavior you're after. We'll need to be able to run and debug such a sample, so I suggest you use either an Access database (which you include in the sample) or the Northwind database from SQL Server.
yes i am loading that grid asynchronously on button 1 click .....
is there any posibility to commit those changes i made to cells should be applied to grid before i do another post back?????
Are you re-binding your grid on a postback/callback, such as in the Page_Load event handler? This is a common cause for changes to be lost.
Are you persisting your changes in some fashion? If you're bound to a SqlDataSource or similar control, this should be handling the persistence for you; otherwise, you may need to handle grid events to store any changes (possibly using a way that will persist across postbacks/callbacks, depending on your setup), and commit those changes in your button click.