diff options
| author | Martin Geubelle <mge@odoo.com> | 2018-04-11 14:47:03 +0200 |
|---|---|---|
| committer | Martin Geubelle <mge@odoo.com> | 2018-04-12 10:10:08 +0200 |
| commit | 729ff2d35eeac7db8cf5fa16009d5c918ee1dd5b (patch) | |
| tree | df6a065d95e69cb63f27f3943640c4dba3e37389 /addons/base_import/static/src/xml | |
| parent | 73425edfe9e03c8ea7e97ab9d7cd6eddec718849 (diff) | |
[FIX] web: update column in grouped kanban
In a kanban grouped by many2one with a progressbar, after emptying a column
by moving all records, the column wasn't correctly updated. This was causing,
in the best case, a record duplication or, in the worst case, a traceback.
This issue comes from the fact that, with a progressbar, a read_group is
performed each time a record is moved. When the group (column) becomes empty,
the read_group won't return this group even though the group still appears in
the kankan. When moving back the record in this empty column, there is a
desynchronization between the kanban controller data and the model.
To fix this issue, an option `keepEmptyGroups` is passed when performing the
mentioned read_group ; this mimics the kanban display that keeps empty groups
displayed and there is no desync anymore.
Fixes #23982
Diffstat (limited to 'addons/base_import/static/src/xml')
0 files changed, 0 insertions, 0 deletions
