Then after those explained, my opinion is that a "Save and close" operation should be performed when switching views.
Because the initial problem was not whether the database is updated or not, but the filed once with a value, after switching views loses the value, and I think that is a bug. Thanks, Mihai -- You received this bug notification because you are a member of C2C OERPScenario, which is subscribed to the OpenERP Project Group. https://bugs.launchpad.net/bugs/789964 Title: mrp - work order in manufacturing order - switching between form - list view does not save data Status in OpenERP GTK Client: Opinion Bug description: Go to a manufacture order with several work orders Scenario 1 In work order tab go to work order 1 and edit the time, mine is 0 so I change to 1 press save and close -> the time is saved (is 1) Press the little list button "change" -> in the form view the time is 0 again Scenario 2 In work order tab Press the little list button "change" And change the time to your wish, press next arrow to change the next time and so on. Wen you press again the list button, the element that was active will lose the time setting. Thanks for this great product! _______________________________________________ Mailing list: https://launchpad.net/~c2c-oerpscenario Post to : c2c-oerpscenario@lists.launchpad.net Unsubscribe : https://launchpad.net/~c2c-oerpscenario More help : https://help.launchpad.net/ListHelp