diff options
| author | David Monjoie <dmo@odoo.com> | 2017-08-04 15:36:31 +0200 |
|---|---|---|
| committer | David Monjoie <dmo@odoo.com> | 2017-08-08 10:38:16 +0200 |
| commit | 587751aa0dbd095db99e93398cf98d705c35679c (patch) | |
| tree | 605380866566644371a4c62770aef4d7bf1ea1d5 /addons/web/static/src/js/views/basic/basic_controller.js | |
| parent | c294e7d46e220ac4e9190c1e1230e34601156177 (diff) | |
[FIX] web: prevent virtual datapoint creation when no default value
Previously, it used to create a virtual datapoint even though there was
no change on this field. If the field was a many2one, this datapoint
triggered a name_get call afterwards, but giving the virtual id of
the datapoint since there is no real record. The solution is to avoid
creating a virtual datapoint when it is not needed at all, thus fixing
the wrong name_get call.
Steps to reproduce the bug:
- Enable lots in Iventory
- Choose a product which is a component of another (through mrp bom)
- Set this product as tracked by lot
- Set this product inventory quantity to 0
- Create a new manufacturing order for the product for which it is a
component
- Click on "Check Availability"
- Click on Produce
- You'll get an error as the web client tries to fetch the name_get of
this datapoint even though the record does not exist.
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_controller.js')
0 files changed, 0 insertions, 0 deletions
