[18.0][MIG] stock_location_lockdown: Migration to 18.0. #2209
Conversation
Improve README
When forcing an outgoing move and then moving it. Odoo create a negative quant. This quant should not be in the locked location because no quand will go in it and so the negative quant will stay here for ever
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: stock-logistics-warehouse-10.0/stock-logistics-warehouse-10.0-stock_location_lockdown Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-warehouse-10-0/stock-logistics-warehouse-10-0-stock_location_lockdown/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: stock-logistics-warehouse-12.0/stock-logistics-warehouse-12.0-stock_location_lockdown Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-warehouse-12-0/stock-logistics-warehouse-12-0-stock_location_lockdown/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: stock-logistics-warehouse-16.0/stock-logistics-warehouse-16.0-stock_location_lockdown Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-warehouse-16-0/stock-logistics-warehouse-16-0-stock_location_lockdown/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: stock-logistics-warehouse-16.0/stock-logistics-warehouse-16.0-stock_location_lockdown Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-warehouse-16-0/stock-logistics-warehouse-16-0-stock_location_lockdown/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: stock-logistics-warehouse-17.0/stock-logistics-warehouse-17.0-stock_location_lockdown Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-warehouse-17-0/stock-logistics-warehouse-17-0-stock_location_lockdown/
Currently translated at 100.0% (6 of 6 strings) Translation: stock-logistics-warehouse-17.0/stock-logistics-warehouse-17.0-stock_location_lockdown Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-warehouse-17-0/stock-logistics-warehouse-17-0-stock_location_lockdown/es/
ced-adhoc
force-pushed
the
18.0-mig-stock_location_lockdown
branch
from
45894d7 to
aaf775d
Compare
|
/ocabot migration stock_location_lockdown |
|
This PR has the |
|
Hi @rousseldenis could you please check this? Thanks! |
|
Hi @rousseldenis , could you please check this? thanks! |
| block_stock_entrance = fields.Boolean( | ||
| help="if this box is checked, putting stock on this location won't be " | ||
| "allowed. Usually used for a virtual location that has " | ||
| "childrens." |
There was a problem hiding this comment.
| "childrens." | |
| "children." |
|
|
||
| block_stock_entrance = fields.Boolean( | ||
| help="if this box is checked, putting stock on this location won't be " | ||
| "allowed. Usually used for a virtual location that has " |
There was a problem hiding this comment.
Shouldn't be that use case solved by using view locations instead for parents ?
As Odoo avoid putting quants in views.
There was a problem hiding this comment.
IMHO, the comment on this should be changed as you can:
- Define WH/Stock as view
So, this module can be used in a generic way if you want to disallow the storage of products there temporarily (in a more permanent way, see above).
| @@ -0,0 +1,12 @@ | |||
| The aim of this module is to mark internal locations where no product | |||
There was a problem hiding this comment.
This should be refactored as this module can be used in a more generic way.
There was a problem hiding this comment.
Hi @rousseldenis !
From a functional perspective, what happens is that when defining the parent location as a view, it doesn't correctly display the nesting of the child locations in the list view. For this reason, the use case is presented for 'internal locations'
No description provided.