[6.1] sale.order.line.note not insert with the right partner language

[Franco Tampieri]

Situation:

Default language for system en_US
other language it_IT

- Partner with a language it_IT
- User with language en_US

When I create a sale order for the Partner, and insert a sale.order.line of a product that have a description_sale in it_IT language, the note is reported on the sale.order.line not in it_IT but in en_US (the default language of the user).

I've tested on:
server (4293)
addons (7042)
web (2472)

I've attach a patch that solve the problem.

Best regards

Franco Tampieri

[Amit Bhavsar (Open ERP) (amb-openerp)]

Hello Franco,

I have checked your scenario, but I think you might have a misunderstand something..

When you try to Insert sale order line of a product that have a description_sale in it_IT language. That's fine, But note is not in it_IT language. Because It's come from the description_sale at product.product.

Moreover, If you provide description_sale manually under the "Product form view at Description tab". and than try to Insert sale order line. would please try In this way.

Hope this will help for you.

Thanks!

[Franco Tampieri (dr.dran)]

Hi Amit,

I don't understand, but for example why in purchase order the note is populated with the correct description_purchase of the partner language and in the sale order not?

there is the line sample from the purchase.py of the purchase module:

line 758 -763
# - determine name and notes based on product in partner lang.
lang = res_partner.browse(cr, uid, partner_id).lang
context_partner = {'lang': lang, 'partner_id': partner_id}
product = product_product.browse(cr, uid, product_id, context=context_partner)
res['value'].update({'name': product.partner_ref, 'notes': notes or product.description_purchase})

Best Regards

Franco

[Amit Bhavsar (Open ERP) (amb-openerp)]

Hello Franco,

First of all, Sorry for the Inconvenience.

Yes, you are right. "sale.order.line.note" should come with the partner language.

Thanks!

[Paulius Sladkevičius @ hbee (komsas)]

Could somebody confirm if it was fixed already or still waiting a fix?

[Paulius Sladkevičius @ hbee (komsas)]

I can confirm that it's fixed on the v7.0