Hi,
Currently Odoo 7 doesnot handle properly 2 type of costing for separate
companies inside the same instance (average cost for company A and
standard cost for company B for example).
We are using the product_price_history module for multi-company price
logging: would it be a good idea to ch
Hi Eric,
I did a quick scan of our code that could depend on that and at first
glance I would see no issue with cost_method becoming a property.
Regards,
-sbi
On Fri, Jun 20, 2014 at 2:13 AM, Eric Caudal
wrote:
> Hi,
> Currently Odoo 7 doesnot handle properly 2 type of costing for separate
Hi Eric,
I think the problem is the performance issue... The property field are
perfo killer and as this module adds quite lots of read in lot's of places,
we already spend time to make it as quick as possible.
A part from that, I agree on the principle, because of course a same
product should n
On Fri, Jun 20, 2014 at 6:32 AM, Joël Grand-Guillaume <
joel.grandguilla...@camptocamp.com> wrote:
> hi Raphael,
>
> i agree with you, but I remember it was in the roadmap to improve those
> proprty field for v8.. Not aware if it has been done or not...
>
I think I can enlighten you: from what I
Hi,
I've had a think about this overnight. Cost method is actually a rarely
used field and to my knowledge only at inwards reception and update price
to determine whether to update average cost. It is all the unneeded reads
and browses that will kill, therefore my answer is to not read it or bro
5 matches
Mail list logo