Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
I have configured an instance to use no decimals, and use "." as thousand separator. This is used this way un CLP (chilean pesos).
In this situation, when creating a purchase order, the price of the item in the purchase order line, (for example 134.990) removes 990 and try to use 135 as the price. So purchase order line price is being misinterpreted as decimal.
To avoid this, I had to remove the thousands separator and use simply 134990.
Is there a shortcut to solve this?
Thanks
You check "Technical Features" on user Administrator view, in "Access Rights". Next you edit Languages from menu Translations. In the definition of the language set sparators as you need.
Is a Bug.
Change this file:
addons/web/static/js/formats.js
Find this line in function instance.web.parse_value:
case 'float':
tmp = Number(value);
if (!isNaN(tmp))
return tmp;
and change for this (Coment whit //)
case 'float':
//tmp = Number(value);
//if (!isNaN(tmp))
//return tmp;
is working for us
Thousand separator is for display pourposes only.. when you enter number, just enter it as is without any thousand separators and it should be ok...
leave the formatting to odoo, and make sure you enter full number
hope it helps,
may the source be with you ;)(
أنشئ حساباً اليوم لتستمتع بالخصائص الحصرية، وتفاعل مع مجتمعنا الرائع!
تسجيل| المنشورات ذات الصلة | الردود | أدوات العرض | النشاط | |
|---|---|---|---|---|
|
0
مارس 15
|
4901 | ||
|
2
مارس 15
|
9943 | ||
|
Problem with tax included price
تم الحل
|
|
1
يونيو 23
|
243 | |
|
1
ديسمبر 22
|
4779 | ||
|
Sales Unit Price
تم الحل
|
|
1
يناير 22
|
3234 |
1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.
I have configured an instance......... more info about this, how and where?
Where: Entering a new purchase order, then add a product to that purchase order with value like the one I specified. How: selarator defined as [3,0]. Thousands sep: "." Decimal sep "," (comma). also, the decimal precision is defined as "0". Because in CLP, decimals are not used.
I cannot comment in your later post, but that was what I 've done to put thousands separator to run. for "Bole", The problem is, that the price is already defined in the product, so when you pass the focus over it, the price is rounded the bad way. If you put the price by hand without punctuation as you says, everything goes ok, but that approach is not a solution for the day to day user.
As I can see there is no workaround in the use. Could you guys please refer a hint or guideline, so I could think to develop a module in order to fix this? Thanks!
well.. if the price is already defined on product.. there lies the rpoblem... obviously, someone imported a lot of products with prices entered with point ( in your case it should be thousand separator, but during import it was importd as decimal point).. only solution i see now is to reimport products, or write a smart sql to update all prices directly... (my guess will be that no product had a price of 1.000.000 - or two separators - otherwise it would thorw error during import)
Bole, this is not the case. The products had been created by hand, with the cost price correctly entered. If you query the table you can see the price is OK. Then, later, the format in the language was set to [3,0], so there is some onchange process that is misinterpreting the "." presented in the purchase line form, as decimal.