[UPG] Upgraded to version 8, fixed references to new 8.0 views and moved fields that were in product.product to product.template
[fix] remove duplicate view and correct view name
[UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0.
[UPG] stock available immediately, corrected the calculation method of
immediately_usable_qty to take in accountthe sign change in outgoing_qty
(from negative to positive) in version 8.
[FLAKE8]
[FIX] renaming of a class, comment removing, useless code.
[UPD] move out from unported to 8 for update
[fix] remove duplicate view and correct view name
[UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0.
[FIX] renaming of a class, comment removing, useless code.
[fix] remove duplicate view and correct view name
[UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0.
[UPD] move out from unported to 8 for update
[fix] remove duplicate view and correct view name
[UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0.
[FIX] renaming of a class, comment removing, useless code.
[UPD] move out from unported to 8 for update
[fix] remove duplicate view and correct view name
[UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0.
[FIX] renaming of a class, comment removing, useless code.
[UPD] move out from unported to 8 for update
[fix] remove duplicate view and correct view name
[UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0.
[FIX] renaming of a class, comment removing, useless code.
[fix] remove duplicate view and correct view name
[UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0.
[UPD] move out from unported to 8 for update
[fix] remove duplicate view and correct view name
[UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0.
[FIX] renaming of a class, comment removing, useless code.
For weird reasons, force-assigning a move does not associate quants.
action_assign'ing the picking does, and is the same procedure that you
can do via the interface.
Using an already created product can lead to incorrect tests on integrated
environments where other modules modify this product. We create a new one for
avoiding this side effect.
This method is called from the write() method the one how support
multiple records an api.multi method.
I was making some test when I tried to activate the mto+mts option for
multiple warehouse and the next error appears: ``ValueError: Expected singleton``
In order to fix this error I only added a loop to manage the multiple
registers.
