diff options
| author | Denis Ledoux <dle@odoo.com> | 2015-01-09 18:02:48 +0100 |
|---|---|---|
| committer | Denis Ledoux <dle@odoo.com> | 2015-01-09 18:10:38 +0100 |
| commit | 38aa984f31f525539d27f2bf47806352705830ba (patch) | |
| tree | 17e1f1fae82dc42af303788c2dccd84e1da2ef16 /addons/analytic_user_function/analytic_user_function_view.xml | |
| parent | 1e5c68f7a64088d6ff0394f13a471cd74dfe0050 (diff) | |
[FIX] web: avoid rendering fields on one2many list validation
This rev. reverts 91911159f5bc12046d791744ff23562378be047f
The above rev. was a good idea, except that internal_set_value expects the raw value, while the records attributes can be tuples(for instance, many2one are tuple(id, name) or list of command(one2many, many2many).
set_value must be use here, as all fields (js) override set_value in order to handle their value repr (for instance, many2one fields handle the tuple (id,name).
Besides, avoiding the re-render provides a huge performance improvment, as rerendering fields can lead to xmlrpc calls (for instance, re-rendering a many2one field implies calling the name_get method)
opw-620111
opw-622108
Diffstat (limited to 'addons/analytic_user_function/analytic_user_function_view.xml')
0 files changed, 0 insertions, 0 deletions
