c2c-oerpscenario team mailing list archive

["Olivier Dony \(OpenERP\)" <765559@xxxxxxxxxxxxxxxxxx>]

Now about the default sorting order for locations, the default order (_order=parent_left, combined with _parent_order=posz,name) will make the list appear as close as possible to the tree structure of the locations (as in "Location Structure") as we can.
This is the case because "_parent_order" being based on "name" means that they will be sorted by name at each tree level, and then the "_order" will make it so the final list is stored according to the tree structure: top to bottom, left-to-right, depth-first.
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?

It seems much more relevant to show the locations this way, rather than
having a flat list of location names, which does not relate at all to
their possibly very complex layout. Why do you think this is not "human-
readable" or "understandable" ?

As a summary, I see only 2 valid "wishlist" points here, for which we can confirm this bug:
- "complete name" of locations should be a stored field, to make it possible to sort with it (it will not be very different from the default sort though, as the complete name obviously matches the tree structure too!)
- "parent location" could be added by default in the search view (for usability, even though it is simple to search on that using custom search)

-- 
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:
  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