Hello, I must say I agree with Jay here, it would be better to improve the robustness a little bit by avoiding to depend on data records that can be changed/removed by the user.
This wizard only needs the current output location to alter its stock-push configuration. I know that initially this can only be the stock.stock_location_output location, but this works only for the main company, and before any changes are made. It would be possible to attempt to locate the current output location by looking at the warehouse of the company of the current user - and this should give the same result as the current code if done right after install within main company, right? BTW, having location_id = False seems impossible (@diff line 12), as get_object_reference() raises if record is not found! -- https://code.launchpad.net/~openerp-dev/openobject-addons/6.0-bug-725571-rgo/+merge/64519 Your team OpenERP R&D Team is subscribed to branch lp:~openerp-dev/openobject-addons/6.0-bug-725571-rgo. _______________________________________________ Mailing list: https://launchpad.net/~openerp-dev-gtk Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-dev-gtk More help : https://help.launchpad.net/ListHelp
