I wanted to ask opinion on a "by-design" issue i have encountered in the web app.

The scenario: make a change in a web app via the model editor to hide a sensitive column in a nested listview, update the app, update the remote web site, and presto, the changes are NOT applied until the end-user wipes cookies.

I contend this is an incorrect design and that cookies must be version-oriented, to ensure validity of display.

To compound the insult of this, column width setting in the same nested listview are not cookied and thus reset every time.

You can see the issue here. thanks, drew..

 Drew,

  I cannot agree with you more.  I have not come across this scenario yet, but I am certain that when my user's do, they will not accept my instructions to clear the cookies as a way for the hidden fields to take effect.  I am tracking the issue.

Bob

I, too,  agree and that is why I think that changing the model merging engine to persist its data in database instead of xml files (as it is now) would fix this problem and many other including having the same mechanism for both platforms (Win and Web).

Mohsen

I have also had an issue where deleting a previously cookied column in the model editor resulted in an exception when trying to show the list view as the column referenced in the cookie could no longer be found.

BTW, the same issue exists in the VCL grid controls, but at least there you can implement your own versioned streaming mechanism to invalidate saved user settings when you make a change to the grid in the code (I use the Tag property of the grid as the grid version number). The user has to redo all their settings when I make a change to the grid, but I seldom do this, and it will usually only be one grid out of many when I do make a change.

The dx team was kind enough to create an issue in SC for this.. Track if you are interested..

Thanks Drew.

I'm experiencing the same problem ...