diff options
| author | Aaron Bohy <aab@odoo.com> | 2018-02-15 10:09:44 +0100 |
|---|---|---|
| committer | Aaron Bohy <aab@odoo.com> | 2018-02-16 14:28:50 +0100 |
| commit | cf03101447cf572417274f06f232056d6b944237 (patch) | |
| tree | c52db40526ce7ed5caa0baa9d480444c12462dcf /addons/web/static/src/js/views/basic/basic_controller.js | |
| parent | 0017902733bffc3bce1cdaeb8ba512a20a0a8c2c (diff) | |
[FIX] web: BasicModel: fetch nested x2manys after onchange
When onchange RPCs return a command 4 (LINK TO), the res_id of the
record to link is given, and the BasicModel has to read the fields
in the view for that record. When one of those fields is an x2many
(for instance, displayed with widget many2many_tags), the
subrecords in the relation must be read as well (at least their
display_name).
Before this rev., this last part wasn't done by the BasicModel, and
as a consequence, the many2many_tags widget was always empty, even
though there were records in the relation.
Same thing applied to reference fields, but this is way more
uncommon.
This rev. ensures that x2manys and reference fields are correctly
fetched in this scenario.
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_controller.js')
0 files changed, 0 insertions, 0 deletions
