summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/views/basic/basic_model.js
diff options
context:
space:
mode:
authorNicolas Martinelli <nim@odoo.com>2020-02-27 08:06:12 +0000
committerNicolas Martinelli <nim@odoo.com>2020-03-09 08:33:58 +0000
commit121c73246dfe455cfd0a86af7515d28bc0a79661 (patch)
treebe6a363e310e6850bee4965e78af45097582fa6f /addons/web/static/src/js/views/basic/basic_model.js
parent74847914977210b1d5a80c1d586eb1316324d9d7 (diff)
[FIX] stock: change of scheduled date
- Install Inventory, Purchase - General Settings/tick Multi-step routes - In Warehouses/YourCompany Incoming Shipments: Receive goods in input, then quality and then stock (3 steps) - Create a PO and add the same products on 2 lines. One has a scheduled date in the future - Go to transfers, where "Picking List" or "Procurement Group" correspond to your PO => the 3 scheduled_date correspond to Datetime.now() - Validate the first picking (WH/IN) The scheduled_date (resp date_expected) in the remaining pickings WH/INT (resp. stock moves) are changed to the past. This is due to the fact that both moves are merged in subsequent pickings. The cleanest solution would be to avoid the merge in case the expected dates are different. Although this makes sense, that also implies a change of behavior. Therefore, we avoid such situation by preventing the propagation of an expected date in the past, which does not make much sense when propagating. opw-2171509 closes odoo/odoo#47155 X-original-commit: c7b2341b35aabe394a34e14c48a913a8595737fc Signed-off-by: Nicolas Martinelli (nim) <nim@odoo.com> Co-authored-by: Arnold Moyaux <arm@odoo.com>
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_model.js')
0 files changed, 0 insertions, 0 deletions