select flag from python model and tree view ignored in default search view

Hello Stephane,

If the object has the search view defined, then nothing can come into its way to appear into search panel.

If the object has no search view, then fields_view_get() will go for arch + python object both.

Can you give it another try?

May be, it just needs a parser change.

Thank you.

Hello Stephane,

you are absolutely correct, infact this issue is not from client rather its from the framework, if a model does not have a search view defined the framework will look out to build some kind of default search view based on the attribute 'select' from the form view of that model. So I would like to change the project to framework.

Thanks,

BTW, the select attributes from list view are ignored too at the moment. To be fully 5.0-compatible we must change it to select = model.select OR form_view.select OR list_view.select

it's normal because there is a search view. (and all objects must have search views in the future)
putting select="1" on the object indicates that the orm have to create an index, not that the field have to be added in the search view.

Fabien, the reason I confirmed this one is not about objects with existing search views, but about those that don't have any, and for which we create a search view on-the-fly.
The code that creates a default search view at the moment makes no sense: it uses the 'select' attribute from the form view, one that is almost never set!
So we might as well do it in a manner that makes sense and is backwards-compatible (also think of rapid prototyping, when there is no search view yet)

Fixed in revision 3091 <email address hidden>, thanks for reporting ;-)