[Trunk/7.0] groups on search view don't work

> Was this functionality removed?

Not intentionally, it seems it was missed when the search view was reimplemented.

Ok, thanks for your confirmation Xavier

So I will wait for it's re implementation :-)

Linked branch ought fix it, if you want to test it (locally or on the runbot).

Thanks, I tested it and it worked fine locally.

I just wander about whether or not the user should see and/or remove an activated filter which is unavailable (invisible) for him in the filter list.

> I just wander about whether or not the user should see and/or remove an activated filter which is unavailable (invisible) for him in the filter list.

So you'd have invisible filters w/ defaults essentially be user-specific "action domain", a domain applied to all searches of the user which he can't alter or remove?

I don't have a particular need about it, I just felt it was strange while I was testing with the "Customer" boolean filter on partner.

What seemed strange to me was to actually see a filter and being able to remove it. If you can't activate it, why would you be able to disable it?

It might be a good idea to make it also invisible or disable the filter at least it shouldn't be changed as the groups is the to hide it's functionality.

The main use case I see is that you want to hide some filters to low level users to have simplified views for them. So if they don't have to use a filter, I think it should have no effect.

After discussing this with APR, I think it might be too much work and too much risk of bad side-effects for too little value: in-view field invisibility is only advisory (e.g. the field is still visible in advanced search). If you want to put implied non-removable filters, you should use the action (potentially via a server action generating a window action with the right domain & context).

As for removing the field altogether, that strikes me as going against the idea of "invisible", in all openerp views "invisible" means the field is there and active, just not shown.

Ok thanks for having taken a look on that. I think your patch is still needed, though, and will be enough in order be able to set invisibility on search field. It is needed to be able to hide basic searches on fields that are not important for a group of users. Even if they can still use it with advanced search, it will be less confusing if simply not displayed in basic search fields.

Fix merged in 7.0 as of revision <email address hidden>