Hi Olivier, Agree with you, if in trunk this is impossible by default, it hasn't sense to apply my patch. But: This fields without product are expensive in cost, but I add these fields in one implementation because I use mixture locations for alcohol factories, then it's important they see how many stock are in the mixture location and how alcohol there are. With trunk patch this operation will be most expensive because I will go around all products in locations and sum his quantities.
In my opinion you must apply my patch and hide by default stock fields if there isn't product in context like rvalyi say in his bug but don't remove this functionality because it can be useful in occasions. -- 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/800301 Title: stock function fields of stock.location compute wrong quanties Status in OpenERP Modules (addons): Confirmed Bug description: Hi, stock_real, stock_virtual, stock_real_value and stock_virtual_value function fields of stock.location, compute wrong stock quantities if you don't pass in context the product, because in its function _product_value when obtaining the products whose get the stock, it gets products from currently location origin moves + currently location destination moves, then it will have duplicate products if in this location had stock entries and outputs of same product. Check this logic, I see this issue showing these fields in stock.locations tree view. I attach a patch. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/openobject-addons/+bug/800301/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~c2c-oerpscenario Post to : [email protected] Unsubscribe : https://launchpad.net/~c2c-oerpscenario More help : https://help.launchpad.net/ListHelp
