c2c-oerpscenario team mailing list archive

["Nhomar \(Vauxoo\) - http://openerp.com.ve" <nhomar@xxxxxxxxx>]

Hello Raph.

I don't understand how are you relating pricelist on this issue, thanks
for the advice, but, in our try, (we are implementing in a 4 companies
enviroment) i think the product_multi_company is right in the definition
of fields, i don't know if you check it (the module) already, but the
problem is that every single sql view to make some reports will broke
because the field was moved to other table.

IMHO this 2 fields must be properties, I  don't know how i didn't see
this already several months ago before release, IOH, i believe that the
R&D team of openerp, can manage simplest reports or complicate the
existent ones, but i'm making a deeper analisys and i can not find other
problem just with reports....

>From My point of view, if a sql view will broke a feature, i delete the
sql view.... not the feature..... and this one is not just a feature is
a Conceptual BUG....

Some comment? from community.

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

Title:
  [TRUNK] standard_price and list_price must be properties.

Status in OpenERP Modules (addons):
  New

Bug description:
  Hello.

  IMHO if we are saying that OpenERP works multicompany out of the box,
  so this 2 fields must be properties.

  In 90% of cases prices are DIfferent not equals between companies.

  Thanks.

  PD: There are a module called product_multicompany, but it broke some
  sql reports, i don't find already another problems in the use of this
  feature....

  We are working in a Solution soon!

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/815436/+subscriptions