Thanks for reviewing this Olivier. Technical side : The Fields.related will take an impact only once the record is saved, and will not have the desired effect on onchange. This way, fields.dummy have an edge to fields.related in this case. At the other hand, reopening the saved form will give us a hint that fields.related will be a better option. As a solution, I opted to override write() as shown above. As an overall effect, to have less(negligible) burden on server, I chose this approach.
Functional side: I agree this is not a bug, but yes, it adds a nice handling of allowing stock handler to assign Lots as and when needed.Consider the same way like having required accounts on journals of type=cash. If I am not mistaken, this lot number will be used as a reference when we have nothing coming from supplier as an initial inventory. This bug has been communicated for maintenance contract by Jba. Thanks again, your feedback is always appreciated. -- https://code.launchpad.net/~openerp-dev/openobject-addons/6.0-bug-700928-jvo/+merge/55334 Your team OpenERP R&D Team is subscribed to branch lp:~openerp-dev/openobject-addons/6.0-bug-700928-jvo. _______________________________________________ Mailing list: https://launchpad.net/~openerp-dev-web Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-dev-web More help : https://help.launchpad.net/ListHelp
