summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/views/basic/basic_view.js
diff options
context:
space:
mode:
authorJorge Pinna Puissant <jpp@odoo.com>2018-12-17 14:31:47 +0000
committerJorge Pinna Puissant <jpp@odoo.com>2018-12-17 14:31:47 +0000
commit8fe7229e1984811f3456dbf502cb03fba879e180 (patch)
tree402613eb1322e0cfb48ba41169969f8a83cdb07b /addons/web/static/src/js/views/basic/basic_view.js
parenta473a1bb88bf930023abc21f270eec0bd1403fb3 (diff)
[FIX] sale_stock: fix onchange product_uom_qty
opw-1916064 Have a sales order line on which you decrease the quantity. Before, this commit, the warning message that says to update the delivery order did not show. This was because, the onchange in the python side compared the new quantity against the saved one, and did not find any difference. This is caused by the onchange itself, which, in a o2m setting, received from the JS, the changed order (already containing the changed line) and only then proceeded to the onchange of the line. The first operation wrote onto _origin the new line value, which corresponded subsequently to the new value. After this commit, we compare the real value explicitly retrieved from the database to the one just entered by the user as an onchange. The warning message works as expected. Long story short, _origin in an onchange doesn't guarantee to yield persisted values in all cases. closes odoo/odoo#29582
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_view.js')
0 files changed, 0 insertions, 0 deletions