diff options
| author | Denis Ledoux <dle@odoo.com> | 2015-04-03 10:59:24 +0200 |
|---|---|---|
| committer | Denis Ledoux <dle@odoo.com> | 2015-04-03 11:06:49 +0200 |
| commit | 83e8c54637e26bb2cc59a69b889f49ec56218272 (patch) | |
| tree | 030cb71ced80d383b7fe04769330a998613cf1ae /addons/analytic_user_function/security/ir.model.access.csv | |
| parent | c06a9696123daae1a2aca0fbdae465d5a8ddc275 (diff) | |
[FIX] product: import product.template fields using default_code
This rev. is related to 489a96c2572bbe2cc04c0658ed2b862aca31fc0f
It wasn't possible anymore to perform an import of
a product.template field in a model
(e.g. mrp.bom), while it should be the case.
In the context of an import,
the operator of the name_search is '='.
Therefore, in this super call, the operator was '='
and the name was '' (empty).
In such a case, ('name', '=', '') is added
to the search domain by the base name_search method
(in models.py),
leading to the domain
[('id', 'in', template_ids), ('name', '=', '')]
which will lead to no results.
Forcing 'ilike' as domain is correct, as the actual
name_search, with the correct operator,
has already been performed in the lines above, the
point of this second name_search is to get
the right order along with the right name_get.
opw-632089
Diffstat (limited to 'addons/analytic_user_function/security/ir.model.access.csv')
0 files changed, 0 insertions, 0 deletions
