Hi Yudi, thanks for your reply. So in other words, any Strict doctype is not supported. Did I get that right? Is support for that planned for the future? We need to get away from these old Transitional doctypes and right now only WebGrid stops us from doing so.

Hi Handy,

Thanks for your reply. Maybe you misunderstood me. I don't want to do anything with the Sum or the Footer. So I don't need to put the sum into any hidden field. The sum is just to block saving as long as the total is not 100%. We don't need to bother with that right now.

I want each individual value of the rows. So if someone edits five rows, I need these five values in the postback. If I understood you correctly, I should dynamically create hidden fields for every editable field. If the grid has two editable columns and a content of 6 rows, I would need to create 12 hidden fields. Then in ExitEditMode js event store the edited field by assigning the value in the correct field and in the postback read out all hidden fields, find the right ones and do the save that way. Is it that what you meant?

If yes, then I would still need to avoid postback after editing and changing the row selection to avoid that the values get overwritten after the postback. How would you do that?

Eric

Hi,

We don't need to discuss the footer, even if there is a bug there. Maybe you're just not using WebGrid6 or you selected another row instead of just pressing Enter or whatever. The footer is not the problem.

FlyPostBackSettings are set to true for all four attributes already (maybe not in the sample though).

What we need is a grid that

- displays database data

- The user can change values in one column, in several different rows before it gets saved.

- Buttons (outside of the WebGrid) to add a new row (requires postback to server to get all data to get added to the new grid row, also requires a popup to select what to get added) But leave this requirement away for now.

- When the user presses a Save button there should be a postback to the server and there all changes get stored in the database at once.

Problem right now: When changing a row, there is a postback to the server which causes the InitializeDataSource event, re-reading the database and overwriting all previously changed data in the grid. How should this get solved?

I think I have to implement the UpdateRow event and store the changed data in the ViewState or something like that. What is the recommended way to implement something like that?

Best way would be to avoid a postback to server until the user presses the Save button, but I'm not sure if that's possible. Other controls (like textboxes) maintain their content in the ViewState even during a postback, but this doesn't work for the WebGrid data when AutoDataCaching is off.

Eric

Hi Yudi,

Thanks for your reply and the link. I downloaded the .chm file, but that documentation doesn't seem newer than the one I have installed with the product.

Also, please note that .chm files don't work by default in corporate environments. Desktop and homedrives and other users' folders are usually on a network share and .chm files on network shares cannot open. But I managed to get around this restriction.

That ISRes_Registered is for SmartWebResources answers this specific question. But it is not even mentioned in the documentation.

And the other values are only minimally described. The values for ViewStateItems for example are not listed, but there's a screenshot that says that there's a GUI to change the values and from there I would be able to extract the possible values (still not having a description for each value though).

So overall, there is no comprehensive documentation available. As I don't have any specific questions, I think we can close this thread. But maybe you got the message to improve the documentation for future releases.

Thanks,

Eric

Hi Handy,

Your answer sounds a little funny, but the roadmap attachment fully answers my question.

From what is said there: Next release of WebUI Studio 2011 R2 / WebUI Studio for ASP.NET includes WebGrid Enterprise 8 and will come out this month and has "improved security by eliminating XSS exploit through the use of JSON as the control data format".

Let me know if I misunderstood anything.

Thanks,

Eric