diff options
| author | Aaron Bohy <aab@odoo.com> | 2019-02-19 10:10:47 +0000 |
|---|---|---|
| committer | Aaron Bohy <aab@odoo.com> | 2019-02-26 08:26:51 +0000 |
| commit | 6a8e1b53e3a01a74aa21b834964994e8d186b653 (patch) | |
| tree | 5c0d9090324775757300692ef1d4c7b6281ec15f /addons/mail/static/src/js/composers/basic_composer.js | |
| parent | a76a958ca8479c3ea0c480bac730f7bfd62ce1d5 (diff) | |
[FIX] web: search more in many2one: filter on ids
Let's assume a many2one field with a lot of possible values. The
user clicks on 'Search More...'. In the opened dialog, only 160
records are available (their ids have been obtained with a
name_search, with the optional text the user could have typed in
the many2one input).
Before 4cd379cf, that extra domain on ids was removed automatically
as soon as the user interacted with the search view in the dialog.
This was especially useful when there were more than 160 records.
However, this was rather an happy coincidence than a designed
feature.
From 4cd379cf, the ids selection was added to the initial domain
of the list, so they couldn't be removed from the domain
afterwards. The user was thus stucked with its preselected 160
records.
This rev. doesn't restore the former behavior, but rather improves
the current one, as follows:
- when there is no text in the many2one input (i.e. no value to
filter on), we bypass the name_search, s.t. all records are
available in the dialog
- when there is some text in the input, we perform a name_search (as
before) to get a list of record ids, and we add a special filter
to the search view in the dialog (the filter on those ids), s.t.
the user can remove it if he wants to access the remaining records.
- finally, the limit is now set to 320, to mitigate the problem
Issue reported on the saas-12.1 migration pad.
closes odoo/odoo#31232
Diffstat (limited to 'addons/mail/static/src/js/composers/basic_composer.js')
0 files changed, 0 insertions, 0 deletions
