The location_id field is important and its value is required, we need to add it
to the wizard (even if it is hidden) so that it is saved and the picking is
created correctly.
Before, the location_id value was only saved (although the field was not in the
wizard) if the user had the "Technical / Manage Multiple Stock Locations" permission.
Extra changes:
- Change reception_move_ids to reception_move_id
- Add test_rma_replace_pick_ship
- Code and method reduction to simplify logic
- Set route_ids (in/out) from procurements
Co-authored-by: Michael Tietz
TT48789
* Standard procedure.
* Transfer view groups to nodes.
* Adjusted upstream changed field names.
* Converted onchanges to computed writable fields.
* Replace `Form` by direct dictionary vals in record creation, as they
don't handle now properly multiple existing fields in the view, and
computed writable improve the compatibility on new values.
* Replace domain returned on onchange by static domain in field.
* Change maintainer.
TT44213
If we place an RMA from the stock picking return wizard, we want to
avoid setting the new moves to refund as that will affect the related
sale lines delivered quantities count.
TT42021
Sometimes there's no choice to return, refund or replace an RMA for
different reasons. For example, when the customer doesn't want to repair
the product because that would be too expensive. We still want finish
the RMA and document the reasons. This improvement allows it.
TT34164
- Fix thrown error when trying to download a picking from the portal.
- Add the hook method to prepare RMA values from the return pick wizard.
- Add the access rule for portal users.
- Show the portal 'Request RMAs' button on the sales page only to users
related to the sales order.
[UPD] Update rma.pot
rma 12.0.1.3.0
Update translation files
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.
Translation: rma-12.0/rma-12.0-rma
Translate-URL: https://translation.odoo-community.org/projects/rma-12-0/rma-12-0-rma/
