On 30 Sep 17:02, Jordi Esteve (Zikzakmedia) wrote: > El 26/09/14 a les 19:35, Cédric Krier ha escrit: > >On 26 Sep 18:41, Jordi Esteve wrote: > >>On 26/09/14 18:08, Albert Cervera i Areny wrote: > >>>2014-09-26 17:59 GMT+02:00 M. Murray <[email protected]>: > >>>>Hello Everyone, > >>>> > >>>>I have a question regarding the search query builder in the tree view. It > >>>>is > >>>>the window that pops up when you click the "Filters" button/label at top > >>>>left. > >>>> > >>>>How can I modify the list of fields that shows in that popup? > >>>Just change the tree view. You can search on all the fields of the > >>>view except those that are not searchable (usually calculated fields) > >>>and the client also adds some special fields such as id, create and > >>>write date and users. > >>> > >>>Note that you can add fields to the view but make them "invisible" so > >>>they're searchable but are not shown to the user. > >>Adding filter fields with a more flexible way than changing the tree view > >>would be a nice feature for Tryton. In my experience, the user wants to > >>search by a lot of criteria, no only by the fields showed in the tree view. > >>This requirement is very common in party and product views. > >> > >>I don't know if other people has this need and if it would be very difficult > >>to implement in the core of Tryton. > >I'm strongly against, it is a wrong user experience to not show proof of > >the result of a search. > > IMHO it is not essential show proof of the result of a search in the tree > view. The users are -normally- intelligent enough to change to form view and > check the search criteria is met.
And how do you check for thousand records? Sorry but when I do a SQL query for example, I always select columns that I use in the where clause to be sure to not make mistake. Human makes mistake and we should do our best to help them to fix them. > In addition, the number of fields where to search usually is bigger than the > number of fields needed in tree view. For example, with some tryton standard > modules installed, you can have 20 fields in the product.template form view > and maybe you want to search product templates by any of these 20 fields, > but it have no sense have all these 20 fields in the tree view. Probably and it has no sense to have to search on all of them. > In addition, currently tryton not always show proof of a search. For > example, by the definition of search_name in parties (you can search a party > by his name or his code) Name and code are on the view. > and in invoices (you can search an invoice by its > number or its party), you can search an invoice in the invoice tree view by > the party code, and the results don't show proof of the search. The code of the party is show in the party column. > In conclusion, IMHO it is not essential show proof of the result of a search > in the tree view. And my experience show that it desirable that an ERP has a > powerful and flexible way to search data. I can not agree, my experience shows that if you don't provide clear information mistakes are made. By the way, you did not give any hint on how to decide which fields should be included in the search by default. And if you answer all of them, it is completly wrong because there are fields that should never be shown to users. -- Cédric Krier - B2CK SPRL Email/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
pgpxyKImMqjw4.pgp
Description: PGP signature
