[6.0] cannot search partner by 'ref' code in custom filter when not using en_US
Bug #701100 reported by
Raphaël Valyi - http://www.akretion.com
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo GTK Client (MOVED TO GITHUB) |
Fix Released
|
Medium
|
OpenERP sa GTK client R&D |
Bug Description
Hello
I think lot's of companies, will have some 'ref' code for their partners and they need to use it as a search field.
So I think we would better have an index on it + have it in the default partner search view.
Any good reason not too?
Related branches
lp:~openerp-dev/openobject-client/trunk-bug-701100-nch
- OpenERP sa GTK client R&D: Pending requested
-
Diff: 59 lines (+14/-7)1 file modifiedbin/widget_search/custom_filter.py (+14/-7)
Changed in openobject-client: | |
assignee: | nobody → OpenERP sa GTK client R&D (openerp-dev-gtk) |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in openobject-client: | |
status: | Incomplete → Confirmed |
Changed in openobject-client: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It's available in:
- the tree view (only if you use the extended view).
- the name_search (so selecting a partner from a many2one (SO, PO, ...) will search on ref=)
It's not in the search view because we tried to limit to search view to important fields, max 5 fields per width. (you can still on the "+" icon to add a filter on any field). The 5 fields are: name, contact, country, category, saleman. The ref is not as important as one of those.
I think that using code for partners is a bit "old school". Most of the customers will not use a code for each partners, that's why it's in extended view only. The customers that needs this are those that migrated from an old software that managed partners using codes in the many2one fields.