-
Notifications
You must be signed in to change notification settings - Fork 23.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FW][FIX] stock: create picking on mobile #144282
[FW][FIX] stock: create picking on mobile #144282
Conversation
@svs-odoo @Whenrow cherrypicking of pull request #143776 failed. stdout:
stderr:
Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?). In the former case, you may want to edit this PR message as well. More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port |
908350a
to
d6c8621
Compare
@Whenrow Something to check: this PR removed the |
997cb16
to
9837a96
Compare
9837a96
to
4039e2f
Compare
Before this commit, it was not possible to create a new picking on mobile if this picking has multiple moves. How to reproduce: - Open Odoo on mobile (or on desktop but simulate mobile device with devtools); - Inventory > Operations > Transfers; - Create a new transfer (a receipt for example); - In its operations (moves), add a new product, then add a second product. - Try to save or validate the picking -> A warning prevent to do it, saying you're trying to write on the field `product_qty` instead of the field `product_uom_qty`. What's happening: For a unknown reason, the fields from the `stock.move` list view are saved once a second move is created, even if we're using the kanban view in the mobile version. To avoid this issue, we force the `force_save` to be false for the field `product_qty` in the kanban view. That's way, it prevents the issue. OPW-3577844 X-original-commit: 818e7fc
2325817
to
9b89f4b
Compare
The `stock.move` form view used for the detailed operation is also used when using Odoo on a mobile device and is not usable in such case (for example, the `product_id` is readonly.) To fix this issue, the view is modified this way: - The `product_id` is readonly only if the move has a id or already a move line (that way, the field is editable when creating a new move but is still readonly otherwise); - The `move_line_ids` is readonly until the move's product is set; - The demand qty. and the UoM are editable if the move is draft. Also, some similar mofifications are done to the `stock.move.line` form view too. OPW-3577844
When creating a picking on mobile, the moves are displayed as kanban boxes. But before this commit, only the mvoe's `quantity` is displayed, that means when in draft, the quantity is usually at 0 and it's the demand (`product_uom_qty`) who is relevant. To fix that, display both fields. Also, we display the UoM aswell if the UoM is enabled.
9b89f4b
to
9dcd878
Compare
robodoo r+ rebase-ff |
Merge method set to rebase and fast-forward. |
Before this commit, it was not possible to create a new picking on mobile if this picking has multiple moves. How to reproduce: - Open Odoo on mobile (or on desktop but simulate mobile device with devtools); - Inventory > Operations > Transfers; - Create a new transfer (a receipt for example); - In its operations (moves), add a new product, then add a second product. - Try to save or validate the picking -> A warning prevent to do it, saying you're trying to write on the field `product_qty` instead of the field `product_uom_qty`. What's happening: For a unknown reason, the fields from the `stock.move` list view are saved once a second move is created, even if we're using the kanban view in the mobile version. To avoid this issue, we force the `force_save` to be false for the field `product_qty` in the kanban view. That's way, it prevents the issue. OPW-3577844 X-original-commit: 818e7fc Part-of: #144282
The `stock.move` form view used for the detailed operation is also used when using Odoo on a mobile device and is not usable in such case (for example, the `product_id` is readonly.) To fix this issue, the view is modified this way: - The `product_id` is readonly only if the move has a id or already a move line (that way, the field is editable when creating a new move but is still readonly otherwise); - The `move_line_ids` is readonly until the move's product is set; - The demand qty. and the UoM are editable if the move is draft. Also, some similar mofifications are done to the `stock.move.line` form view too. OPW-3577844 Part-of: #144282
Before this commit, it was not possible to create a new picking on mobile if this picking has multiple moves.
How to reproduce:
product_qty
instead of the fieldproduct_uom_qty
.What's happening:
For a unknown reason, the fields from the
stock.move
list view are saved once a second move is created, even if we're using the kanban view in the mobile version.To avoid this issue, we force the
force_save
to be false for the fieldproduct_qty
in the kanban view. That's way, it prevents the issue.OPW-3577844
Forward-Port-Of: #143776