← Back to team overview

openerp-community team mailing list archive

Re: Individual column filtering in Odoo


This is a return to the 6.1 style, but in this use case I think it works
very well – intuitive and less work for the user when applying multiple


*From:* Openerp-community [mailto:openerp-community-bounces+rcarnes=
ursainfosystems.com@xxxxxxxxxxxxxxxxxxx] *On Behalf Of *Luc De Meyer
*Sent:* Thursday, June 19, 2014 1:02 PM
*To:* 'David Arnold - El Alemán'; 'Olivier Dony'
*Cc:* openerp-community@xxxxxxxxxxxxxxxxxxx; 'Oscar Alcala'
*Subject:* Re: [Openerp-community] Individual column filtering in Odoo

You can have a look to the ‘account_move_line_search_extension’ (community
module available from apps.odoo.com) as an example of how to search through
a massive amount of journal items in an intuitive way.

Without this small module, some of our customers would simply forget about
Odoo and move to other solutions.




Rusatiralaan 1, 1083 Brussel

+32 2 808 86 38

[image: cid:image002.jpg@01CE271A.FF53FB90]

*From:* Openerp-community [
<openerp-community-bounces+luc.demeyer=noviat.be@xxxxxxxxxxxxxxxxxxx>] *On
Behalf Of *David Arnold - El Alemán
*Sent:* donderdag 19 juni 2014 15:16
*To:* Olivier Dony
*Cc:* openerp-community@xxxxxxxxxxxxxxxxxxx; Oscar Alcala
*Subject:* Re: [Openerp-community] Individual column filtering in Odoo

Despite of all details, https://datatables.net/ seems a great NIH-tool.

In some cases I'd prefer disruptive moves over evolution.

I think it's worth taking a closer look at it, not thinking about how the
same functionality can be achieved with the concurrent solution, but just
admiring the beauty and responsiveness of this benchmark.

look for example at Scroller: https://datatables.net/extensions/scroller/

or colreaorder: https://datatables.net/extensions/colreorder/

or colvis: https://datatables.net/extensions/colvis/

and type in "acc 16" -> this doesn't work in odoo, the "benchmark-way".


*David Arnold B.A. HSG*


+57 315 304 1368



​El Alemán S.A.S, Carrera 13 # 93 - 40 P4, Bogotá D.C, Colombia

2014-06-19 6:51 GMT-05:00 Olivier Dony <odo@xxxxxxxxxxx>:

On 06/19/2014 01:27 PM, Pedro Manuel Baeza Romero wrote:

I agree with Olivier that the way to go if you want to search directly for
certain field is to include it as a search field on the view, and going down
with the arrows, but please improve saved filters, recreating in the same
as you put originally filters and group by options before saving the filter,
and not grouping them in one facet. This would be a very huge improvement

Pedro you're right, and we have looked into doing exactly this: restoring
the search state of a saved filter by splitting the criterions into search
facets, etc.
The problem is that filters are implemented as a (domain, context) pair in
order to provide the best flexibility. It's great because you can make very
advanced custom filters, but it's a problem if you want to map this to a
search view state, because it's impossible (meaning: not computable)

One option would be to save some sort of extra serialized state of the
search view when you save a custom filter, and attempt to restore it when
you use the saved filter (possibly falling back to the current behavior
when it fails).
This is far from trivial but would be very useful indeed.
If anyone wants to work on this, we could discuss it with @xmo-odoo, he
designed the v7 search views.

Mailing list: https://launchpad.net/~openerp-community
Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

PNG image

JPEG image