Resorting Library Items Saves Without Confirmation
Description
Environment
is related to
Activity
Frederic Altorfer December 21, 2010 at 11:11 PM
Changed the library picker behavior. Selecting, sorting or removing library items will not affect the objects relation table till you save.
Sean Coyne October 10, 2010 at 12:49 AM
This also affects the library. Each time you change pages with the pagination links, it saves to the database. That's the real root issue here. The data shouldn't be saved to the database until explicitly told to. This would be when the user clicks the "Save" button on the main form.
I would suggest the data is stored and retrieved from a temporary storage location, the session scope, the Wizard's WDDX, etc. The database, the actual live record no less, is not the place for this data. Until the user clicks the save button, it should be considered temporary data.
Jeff Coughlin October 10, 2010 at 12:42 AM
We are running into more issues with this where this new feature added midway through FarCry 4 is starting to cause some SERIOUS data integrity when you create new records. It's a long explanation that I'll let Sean better explain, but needless to say this is a serious bug that is causing lots of headaches with our clients (and messing up a lot of data.
Geoff Bowers September 25, 2010 at 12:29 PM
Array properties are immediately updated. The only way to get around this is to change the fundamental behaviour of the underlying array property.
MvdO79 July 8, 2009 at 5:12 PM
Using FC 5.1.6 this is still the case, when reordering items in library selected list they get updated when moved, so even when click cancel after the changes are set anyhow.
Using a container popup window (rule) and reordering items in a library (array) it saves the new array order without confirmation.
If you reorder items, then hit cancel (not save) it saves it in the order you last dragged the items anyway (I have not tested this in the webtop as well).
I discovered this while trying to see why reordering items is slower than it used to be (re: FC-980). It appears that an Ajax command is sent upon each reorder (hence the slow reaction times referred to in FC-980). This Ajax call updates the database each time (without waiting for confirmation from the user whether they want to keep this change or not).