Aspxgridview rowupdating e newvalues empty

Rated 4.4/5 based on 504 customer reviews

I have a Grid View control and use old style manual binding with a Data Source property and invoke the Data Bind() method.

If you don't use one of the Data Source controls, you are required to handle the Row Updating event.

Grid View was filled with the old values again, so in my Grid.

Default editor instances are available in the ASPx Grid View. You can access the editor here and save it to a Session.

I ran into two problems with this approach.1) Our site uses SQLServer to store Session data, so I got this error message when trying to store the ASPx Text Box in the Session: Unable to serialize the session state.

aspxgridview rowupdating e newvalues empty-37

aspxgridview rowupdating e newvalues empty-25

aspxgridview rowupdating e newvalues empty-65

It doesn't throw any exceptions, but the controls still contain the old values, not the new values.

I might try that and see if you can assign an ID to a datasource and bind it in code behind.

If not I'll try the suggestion below =) I was doing databinding in my Page_Load event and when I clicked "Update" the Post Back was done, so was the Page_Load event fired.

I'm concerned that Load Post Data Recursive is from the Internal namespace, so it might end up on the wrong side of a breaking change in a future version of the controls. I'm leaving these notes here in case other users find themselves in the same situation. In the Cell Editor Initialize event handler, I add a client-side event handler script to each ASPx Text Box. The script uses an ASPx Callback to send the new value to the code-behind, which saves it in the Session.

We have reproduced the issue and our developers are presently working on it. Load Post Data Recursive method to prevent the mentioned behavior. Hopefully, these hints will help you achieve the desired result. I would rather not use the Session to store the data for 2 reasons: - If user closes browser or browser tab with this page, the data stays in the session. My current workaround is getting old Values from the aspxgrdiview using Get Row Values for the Editing Row Visible Index and getting new Values from the editformtemplatecontrol after using Render Utils. Columns["Category Name"], "Category Name is too long."), the Row Updating event is not called and the Pop Up Edit Form stays displayed on screen. - However, after this validation with error, the Pop Up Edit Form shows the original values instead of the modified values (that contain the error)! Regards, Jenny Dear, Binding the controls in the popup editform (aspx) seems to solve all the issues.

Leave a Reply