diff options
| author | Denis Ledoux <dle@odoo.com> | 2016-06-16 11:24:13 +0200 |
|---|---|---|
| committer | Denis Ledoux <dle@odoo.com> | 2016-06-16 11:32:10 +0200 |
| commit | ae74ebb5ce74b9f62fe1f5222b82983780db2d47 (patch) | |
| tree | 0267ec5ba7dd820c72bf0db266ebd882bae1859b /addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js | |
| parent | 606eab8ef8d904aed9c83f9cb5b61e237b13b586 (diff) | |
[FIX] purchase: `related_usage` must be readonly
The `related_usage` field of `purchase.order`
is a related field to the location `usage` field,
which is defined in order to display/hide
some other field in the PO according to the location usage
This is purely a technical field, which is set only
to change the form view according to the location
usage.
This is not expected to change the location usage
through this field, this field must therefore
be set to readonly.
A change on the location usage could happen because
of the `onchange_picking_type_id`:
If the user changed the picking type, and then the location,
the usage returned by the `onchange_picking_type_id` was
applied on the location, and this must not have happened.
In addition, since `related_usage` is a related to the location
usage, it should be changed as well when the location is changed.
(in the new api, this is no longer required, the related field
is updated automatically).
This revision therefore adds an onchange on the location as well,
to handle this.
opw-676428
Diffstat (limited to 'addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js')
0 files changed, 0 insertions, 0 deletions