[Trunk/7.0] customer > sales order -> wrong pricelist

Bug #1174734 reported by Peter Langenberg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Fix Committed
Undecided
OpenERP Publisher's Warranty Team

Bug Description

http://7-0-7979.runbot.openerp.com/?db=7-0-7979-all#menu_id=153&action=135

Scenario :

1) Duplicate 'Public Pricelist' to 'Public Pricelist XX'
2) Change sales pricelist on customer 'Agrolait' (Sales > Customers) and save
3) Push on button Quotations and Sales
4) Push on button CREATE

The pricelist you get there should be Public Pricelist XX, but you get Public Pricelist !

Tags: maintenance

Related branches

summary: - [7.0] customer > sales order -> wrong pricelist
+ [Trunk/7.0] customer > sales order -> wrong pricelist
Changed in openobject-addons:
assignee: nobody → OpenERP Publisher's Warranty Team (openerp-opw)
tags: added: maintenance
Revision history for this message
Dharti Ratani(OpenERP) (dhr-openerp) wrote :

Hello,

It has been fixed in the following branch : https://code.launchpad.net/~openerp-dev/openobject-addons/7.0-opw-592116-dhr with revison num : 9091
revision id : <email address hidden>.

Thanks

Changed in openobject-addons:
status: New → Fix Committed
Revision history for this message
Rifakat Husen (OpenERP) (rha-openerp) wrote :

Hi,

I think the root problem is the arrangement of the fields in the quotation form.
field customer comes first in the view arrangement and then field shop_id comes and as per the web client
architecture it will first execute customer on_change and then execute shop_id on_change.

As shop_id executes latter, it will fill value of Pricelist based on shop on_change and that's the reason customer's
pricelist is getting vanished.

It indeed needs a tricky solution, putting shop_id before the customer should actually solve the problem(note in previous versions shop_id was before customer, at the top), but that would not look good.

Attached patch will change the placement of the shop(before) and customer fields without changing the GUI feel.
This is just an alternative solution for the same bug report.

Regards,
Rifakat

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.