c2c-oerpscenario team mailing list archive

[Graeme Gellatly <697502@xxxxxxxxxxxxxxxxxx>]

Fabien,

While I understand what you say, it cannot be both ways.  Either when
you change the pricelist it is only for those lines on, or it isn't.
Moreover, I should be able to tell which lines are set at which
pricelist.  The solution you suggest , suggests strongly to the user
that the entire quote would be at one pricing which it isn't.

Besides if I modify an existing line set with an old pricelist (say
change the quantity) it uses the new pricelist.  Heck if I modify the
quantity even when I have manually set the price it uses the new
pricelist.  So to say it is only for those lines on is also not correct.

Besides the effect is not as drastic as you make out.  You change the
pricelist - all the prices change - oops thats not what i wanted -
change the pricelist back.  Far less drastic than some current
behaviour.  Change any quantity after setting a price manually and lose
your pricing with no way of getting it back.

Personally I think normal behaviour is it should be one pricelist per
order and that pricelist determines pricing unless manually overidden.
I will implement as an addon but this is an error in functionality IMO.

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

Title:
  [sale][trunk]changing pricelist does not change prices in sale order

Status in OpenObject Addons Modules:
  Invalid

Bug description:
  Scenario. Same quote to 2 customers on different pricelists.

Create 2 pricelists A & B
Create quote and save at price A.
Duplicate quote and change pricelist to B.  
Price does not change.

Next Scenario. Customer phones and wants better price
Use existing quote A and change pricelist to B.
Price does not change.

Next scenario. I just typed out a big order, then realised I used wrong pricelist, change pricelist, but price does not change.

However if I go in to each order line and trigger on_change in those fields price updates.

Latest revisions as of yesterday.  Seems like an on-change function is required for the pricelist field.