diff options
| author | Raphael Collet <rco@odoo.com> | 2020-05-06 09:37:01 +0000 |
|---|---|---|
| committer | Raphael Collet <rco@odoo.com> | 2020-06-11 14:40:33 +0000 |
| commit | 150f68108c0a1570f7b2822a7ba575029160ce4f (patch) | |
| tree | f7873442cf8ce84d132ad173141256e1e82337c3 /addons/web/static/src/js/views/basic/basic_renderer.js | |
| parent | b15c2803699610179945ba690e1e5bc922a6e2b2 (diff) | |
[FIX] core: do not compute a field on a mix of new and real records
This fix looks like good practice to avoid confusing developers when
writing compute methods for fields, and should not be necessary. But it
actually fixes an extremely obscure bug in the computation of the field
`sale.order.invoice_status` when dealing with timesheets (module
sale_timesheet_enterprise). The bug seems triggered by the fact that
the field is computed on both a given sales order and a new record with
that sales order as origin.
X-original-commit: f9c128c6f567dfaab5cfb0080e4fdc847942911a
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_renderer.js')
0 files changed, 0 insertions, 0 deletions