Community mailing list archives

community@mail.odoo.com

Re: Decimal point or comma

by
Ferdinand Gassauer
- 12/03/2015 04:48:58
On 2015-12-03 10:27, Wim Audenaert wrote:

a very good and necessary idea - a long time issue.
<blockquote cite="mid:260CB26B49AA0048BFAFE792C39A22D033AA8DC0@BESRV01.ucamco.com" type="cite">

Hello Pedro,

 

I have been testing your module, and this looks to work great. I will install it in our production environment, and I’ll ask the users to verify the coming days the float fields that are entered.

 

Thanks a lot for your fast answer yesterday evening.

 

Best regards,

 

Wim

 

From: Pedro Manuel Baeza Romero [mailto:pedro.baeza@gmail.com]
Sent: Wednesday, December 2, 2015 8:47 PM
To: Community <community@mail.odoo.com>
Subject: Re: Decimal point or comma

 

We have this module: https://github.com/odoomrp/odoomrp-utils/pull/57, but it's not fully-tested. Please try and tell us.

Regards.

 

2015-12-02 20:37 GMT+01:00 Wim Audenaert <Wim.Audenaert@ucamco.com>:

Hello,

 

We migrated last weekend finally from version 7 to version 8.

 

In Belgium, we are used  to work with a decimal comma, and some companies also use a thousand separator (a point). This is set up correctly in the language definition.

 

In version 7 (without a specific module installed for it), the user could enter a number with a decimal comma (as used also on the documents and reports), or with a decimal point. For your information: the numeric part of the keyboard has a point as decimal separator. Some examples of how it was processed in version 7 (result showing with a comma as decimal separator and a point as thousand separator):

 

·         When the user enters 1234,56… it was displayed after saving as 1.234,56.

·         When the user enters 1234.56… it was displayed after saving as 1.234,56.

 

Since we moved to version 8, the user MUST use a comma as decimal separator. In case that he uses a decimal point, this point is not taken into account as decimal separator. As some of our users enter a lot of numbers, they are losing a lot of user friendliness in the application. Using the same example as above, it is processed in version 8 as:

 

·         When the user enters 1234,56… it was displayed after saving as 1.234,56.

·         When the user enters 1234.56… it was displayed after saving as 123.456,00.

 

As the users were used to use the decimal separator in the numeric part of the keyboard, they already made a lot of errors.

 

I logged an issue at Odoo support last week, but so far I didn’t get a solution. They also can’t reproduce the situation in version 7 as described above.

 

Does somebody in the community knows a solution to fix this issue?


Thanks for your help.


Best regards,

 

Wim

 

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe

 

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe