Steps to reproduce:
1. Go to Contacts (for example).
2. Filters > Add Custom Filter.
3. Select "Company" field.
4. Select "is equal to" operator.
5. Click on "Search more..." button.
6. Select a record.
Result:
An exception is raised
```
UncaughtPromiseError > TypeError
Uncaught Promise > parent._trigger_up is not a function
```
Expected:
It should open the search more dialog, and let the user select a record.
Steps to reproduce:
1. Go to any Pivot or Graph view.
2. Add a custom filter, for example, Company.
3. Use the "is equal to" operator.
Result:
Uncaught Promise > Cannot find the definition of component "RecordPicker"
---
This happens because in Odoo 15.0 there are two versions of the FilterMenu and
CustomFilterItem widgets: one implemented in the legacy widget framework [^1]
and another implemented in Owl [^2].
The legacy version is used for `tree` views, for example; whilst the Owl version
is used for `pivot` and `graph` views.
Confusing as it is, before this commit only the legacy version was being overriden,
making it work for `tree` views (most common case), but not for `pivot` views.
Since both versions share the same QWeb template, though, not only it wasn't
working for `pivot`, but it also raised an Exception.
[^1]: https://github.com/odoo/odoo/blob/21a2dfd90/addons/web/static/src/legacy/js/control_panel/custom_filter_item.js#L45
[^2]: https://github.com/odoo/odoo/blob/21a2dfd90/addons/web/static/src/search/filter_menu/custom_filter_item.js#L107
There is a problem when converting a domain object to an array.
in the case of a combination of several OR operators, the retroconversion into an array
from the domain object is not equal to the original array used for initialization.
The problem can be related to the initialization of the domain object or to the
conversion to an array, but in any case, it is out of this PR scope.
The humanDomain needs an array domain, which mean that the conversion and the
retro-conversion are useless in this case.
Before this patch, when searching with the "equals to" operator in any
x2many field, the searched parameter was always `undefined`.
The problem was that the underlying field manager implementation was
treating those fields as x2many, while the widget used was the `one2many`
one.
This patch simply mocks the underlying fake record to make think that
any relational field is always a `one2many`. This sets all pieces in
place and makes the field manager work as expected, and thus you can
search as expected too.
* Complete migration to v11
* Refactor to use the new v11 decoupled widgets system
* Advanced search is now a high-level feature from the filters menu; it simplifies code a lot, and the UX is even better
* Split README system
* Add fun to ROADMAP
* Addon is renamed to web_advanced_search, since it enhaces the searching experience for all kind of fields now
and replace company icon
[FIX] js syntax
[FIX] move our patched equals operator to top of list
[ADD] support selecting domains on x2x fields
[FIX] eval search view's domain
[IMP] UI fixes
[IMP] reflect recent additions in README.rst
[FIX] typos
[ADD] translations
[FIX] correct js reference
[RFR] rebuild our domains in a different way
this solves timing problems
David
Ivàn Todorovich
Víctor Martínez
Jeroen Evens
Raf Ven
Alexandre D. Díaz
sbejaoui
tarteo
Jairo Llopis
Simone Orsi
Jose Maria Bernet
Benjamin Willig
ralwafaie
Holger Brunn
cubells