summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/widgets/data_export.js
diff options
context:
space:
mode:
authorSimon Lejeune <sle@openerp.com>2019-09-12 13:47:51 +0000
committerSimon Lejeune <sle@openerp.com>2019-09-13 10:09:40 +0000
commite4cba4d0376eda9c58d53c39ee2d6d0281c72c2d (patch)
treee0e9d8fa9c4097f6aabb5105fc6da2c744648b65 /addons/web/static/src/js/widgets/data_export.js
parent3f0ed7d04553c1eeec9eaad4455ff053ddcebf55 (diff)
[FIX] purchase_requisition: supplier info
When a blanket order is opened, a supplier info is created and should be used in priority over a regular supplier info with the same values. That's what rev [0] tried to do but there was some mistakes: the `purchase_requisition_id` field added in the order is ignored since it isn't stored and the test didn't failed because the created blanket has a lower price unit than the regular supplier info, meaning it is used in priority. Setting the same price unit (50) result in the new purchase order line merged in the first one. Do not re-implement the same order. Adapt the test now that we know the order didn't work (see rev[1]). The user has to manually set a higher priority to the supplier info generated by the purchase requisition. [0] e85838d358c20859b37e2560c004ee0dcf405c31 [1] 2ac4f2ee0f26678b304929e3352418871ae11857 closes odoo/odoo#36840 Signed-off-by: Simon Lejeune (sle) <sle@openerp.com>
Diffstat (limited to 'addons/web/static/src/js/widgets/data_export.js')
0 files changed, 0 insertions, 0 deletions