c2c-oerpscenario team mailing list archive

[Christian Sprauer <693460@xxxxxxxxxxxxxxxxxx>]

I would like to emphasis Ferdinand's point here :
>("function/related fields are *not* computed by the orm.read_group(), it is not feasable to explain this to clients/prospects
>/users - they simply do not care about internal limitations.)

The "Group_by" is a key innovation of V6 and it should work seamlessly
for related/ function fields.  Group_by represents huge productivity
gains for end users, because what they typically do today is a) extract
data from the DB into excel, b) make a few functions, c) do a pivot
chart to aggregate the data, d)play with the pivot chart in a graphical
manner to make sense of their data. I have seen this a million of times.
Many end users are familiar with pivot charts and the group_by feature
in OpenERP V6 comes very close in terms of functionality.

In contrast, "SQL based" reports are more powerful but much less user
friendly. They typically require some degree of programming skills
(which means time and money to extract datas that are allready in some
form in OpenERP - this is difficult to explain to customers) and it may
take time until a "user adopted" OLAP module is developped.

I would therefore argue for a high importance of the "Group_by" feature
on related/function field (even if it takes some dirty python for now).
End users will appreciate it and productivity gains may be greater than
with SQL reports, because it's so much flexible to decide what field you
want to group by.

A related problem, which bugs me for some time, is the ability to get a related field directly in a view without defining it as a function field or related field in the python code (apologies if this sounds crazy, I am not an expert programmer), using relationships of relationships syntax like in the rml reports :  sourceobject.relationobject1.relationobject2.relationobject2fieldname ?  
If this later element is not related to this bug please let me know, i will post another bug (or feedback).

-- 
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/693460

Title:
  [6.0 RC1] products  filter location and group  by  category give wrong
  results

Status in OpenObject Server:
  Confirmed

Bug description:
  to reproduce
  clear 
  extra filter location=output (looks OK without investigating the data)
  group by category
  some issues
  - every row shows 0 values
  ** negativ value of virtual stock missing [PC1]
  opening any of the categories - shows all products + quantities (presumably of all stock locations)

  IMHO it's a real drawback not beeing able to filter "Real Stock" 
  Example 
  * "Real Stock" is not 0 
  to show only available products