c2c-oerpscenario team mailing list archive

["Ferdinand @ Camptocamp" <765559@xxxxxxxxxxxxxxxxxx>]

please see the image

@Olivier: 
"If you compare the "location structure" tree and the location list, you should see that the list shows the same result as the tree if it was fully expanded (this depends on the filters of course). Is that not the case for you?"

the structure is correct, but not the list.

at least "I" can not explain to users why this is sorted

but it is relatively simple to create a STORED  'complete_name' which
must  be a bit longer than  100 and which is recalculated for all
children every time the name of a location changes.


** Attachment added: "location sort.png"
   https://bugs.launchpad.net/openobject-addons/+bug/765559/+attachment/2091291/+files/location%20sort.png

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/765559

Title:
  locations cannot be sorted

Status in OpenERP Modules (addons):
  Confirmed

Bug description:
  1. Currently the locations list has limited sorting features, because the "complete name" field is a function field that is not stored.
  Making it stored would improve this, but it must not be "stored=True", otherwise it will not be correctly recomputed when ancestor locations are modified!
  The store trigger must recompute all descendant locations too (child_of operator)!

  2. Adding the parent_location to the search view could be useful too.


  ===== original description =======
  the tree view of stock locations (not location structure - this one is OK) results in a list order by
   _order = 'parent_left'
  which is not human readable / undertandable

  together with the fact that function fields (Location Name = complete_name)  can't be sorted this list is not user friendly at all
  (sorting worked in V5)

  BTW
  IMHO the search view should have buttons for all "usages"
  as well as a search field for parent location

  please consider the missing sorting and filtering of function fields
  as a major issue for migration of complex installations to v6