[18.0][MIG] rma_sale_mrp: Migration to version 18.0#525
[18.0][MIG] rma_sale_mrp: Migration to version 18.0#525eduezerouali-tecnativa wants to merge 33 commits intoOCA:18.0from
Conversation
de70770 to
f301357
Compare
| >data.get('phantom_bom_product') and data['quantity'] or 0</attribute> | ||
| </xpath> | ||
| <!-- TODO: We could give a clue about what's to be returned, with readonly detailed lines --> | ||
| <!-- TODO: We could give a clue about what's to be returned, with readonly detailed lines |
There was a problem hiding this comment.
Why is it necessary to comment on this now? If it is not necessary, the corresponding code should be removed and explained.
09c10e8 to
899ad94
Compare
|
/ocabot migration rma_sale_mrp |
In the wizard, if a component line didn't have any quantity, we could end in an infinite loop when creating the RMA.
[UPD] Update rma_sale_mrp.pot [UPD] README.rst
We must inform the component line maximum qty to return so we're able to properly discount every line on the wizard TT29876
rma_sale_mrp 13.0.2.0.0
- When creating an RMA for a kit from the portal, the description was lost for the components. rma_sale_mrp 13.0.2.0.1
[UPD] Update rma_sale_mrp.pot [UPD] README.rst
As we rely on the kit_qty field have the kit/component relation an that's computed when the RMA is created, we want to avoid reopening the RMA to avoid inconsitencies. The user should create a new RMA. TT41943
- Standard procedure. - Rename changed fields. TT44949
Whenever we tried to edit a line belonging to a kit we couldn't finsish the RMA. The wizard view was unwittingly requiring this field which for the kit line shouldn't be required. TT45051
Currently translated at 100.0% (55 of 55 strings) Translation: rma-16.0/rma-16.0-rma_sale_mrp Translate-URL: https://translation.odoo-community.org/projects/rma-16-0/rma-16-0-rma_sale_mrp/es/
…s with phantom_bom_product set~
Currently translated at 100.0% (55 of 55 strings) Translation: rma-16.0/rma-16.0-rma_sale_mrp Translate-URL: https://translation.odoo-community.org/projects/rma-16-0/rma-16-0-rma_sale_mrp/pt_BR/
The rma operation is required in the portal, and it makes sense for it to be required in the sales wizard as well
Currently translated at 100.0% (57 of 57 strings) Translation: rma-16.0/rma-16.0-rma_sale_mrp Translate-URL: https://translation.odoo-community.org/projects/rma-16-0/rma-16-0-rma_sale_mrp/it/
Currently translated at 100.0% (57 of 57 strings) Translation: rma-16.0/rma-16.0-rma_sale_mrp Translate-URL: https://translation.odoo-community.org/projects/rma-16-0/rma-16-0-rma_sale_mrp/pt_BR/
- Display the allowed quantity to return - Simplify data encoding by adding a button to select/deselect all lines - Ensure that the quantity to return is always less than or equal to the allowed quantity
Currently translated at 100.0% (62 of 62 strings) Translation: rma-16.0/rma-16.0-rma_sale_mrp Translate-URL: https://translation.odoo-community.org/projects/rma-16-0/rma-16-0-rma_sale_mrp/it/
899ad94 to
c57d0a2
Compare
|
@victoralmau sorry for the late replay, now it is working as it should. |
|
@mariancuadranetkia first thank you to take the time for the review. Could you give more detail on how you got the error. Anyways i think it has to do with not valid the picking. |
|
@eduezerouali-tecnativa rma.kit.error.mp4 |
|
@mariancuadranetkia the main problem is that you are using a kit with one product that it is not trackable. Try again creating your own products and components and you will see that RMA is create correctly. |
Mmm yes, but, this way customer can't create RMA to ask for a refund if a product is not trackable or a component of kit is not trackable? Because, I can create a return picking without RMA without problem of this product not trackable, problem it's only creating RMA. I'm not sure if this is the expected behaviour, but, if I can return a product and I can refund it, I don't understand the reason to not allow create RMA to register this operation. |





cc @Tecnativa TT57276
ping @victoralmau @pedrobaeza