diff options
| author | Josse Colpaert <jco@odoo.com> | 2017-12-11 16:47:53 +0100 |
|---|---|---|
| committer | Josse Colpaert <jco@odoo.com> | 2017-12-13 10:17:48 +0100 |
| commit | 22f8660e2211fd84f84f530cfed29a594a228a02 (patch) | |
| tree | af1d7ba66beabfcc2dbadb816f405b5346ee098b /addons/web/static/src/js/views/basic/basic_model.js | |
| parent | 30d0861f0a9c9079c3c2222ca6d1b2a2e33469c2 (diff) | |
[FIX] stock: don't propagate cancel when chained move is done
When you have e.g. an SO with a product MTO generating a manufacturing
order, and you put the delivery order to done, before the MO is done,
you can not cancel the MO anymore, because the cancel method checks if
the move is not done (and raises an error).
As the user stays blocked in this case, it is better to just not try to
cancel the destination move by not propagating the cancel when the destination
move is done.
opw-786571
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_model.js')
0 files changed, 0 insertions, 0 deletions
