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.
We appreciate your patience while we work to find a solution to your inquiry. If you need any further help on this subject, please feel free to reactivate this ticket. This can become a storage problem when having a lot of simultanous users on the server. Load Post Data Recursive for it (as you specified in your answer). If equal, then no db update is needed (values are not dirty).2) How do you add validation to this pop Up Edit Form approach? I can get the new Values from the editformtemplatecontrol and validate it's value. I do not need to load Post Data to the required controls explicitly via the Dev Express.
Thanks, Jenny -Why is it not possible to use the Enable Callback = false in Pop Up Edit Form mode? The cause of the problem is that grid gets its Post Data after the Page_Init event but before the Page_Load event. Data Bind method is called in the Page_Load event handler, it disturbs values returned from Post Data. We recommend binding the grid in the Page_Init event handler. - When the user opens 2 tabs for the same page, the session data is not specific for those tabs and state saved in the session variable can conflict between pages (removed on tab1 but still available on tab2). Viewstate is page-specific and only lives within lifecycle of let's still use session data as you specify, I'll try to solve that later.== I have 2 questions using your example:1) The e.
- How can I my attached example working with a custom edit template using this Enable Callback = false with Pop Up Edit Form mode and edit-visible-only columns ? Get Row Values method and set initial value template controls.
To get the desired result, perform the following steps: 1) Handle the ASPx Grid View.
I have modified our project according to the information above and handled the ASPx Grid View. Please let us know whether this approach suits your needs. Load Post Data Recursive (as mentioned in your previous post) anymore which makes code much shorter and easier to understand. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose.
According to your project, Edit Form template controls are not bound to Data Source. (2) How do you add validation to this pop Up Edit Form approach? Please take a look at the Grid Editing - Validation online demo, illustrating the manual validation. Disclaimer: The information provided on Dev and its affiliated web properties is provided "as is" without warranty of any kind.