Accuracy of float values doesn't match price_accuracy
Bug #459027 reported by
nrumprecht
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Addons (MOVED TO GITHUB) |
Fix Released
|
Undecided
|
Unassigned | ||
Odoo Web Client |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
It's more a problem than a bug,
but if you configure openerp to have a price accuracy of 4 and you have prices for your products
like 12.4432 € and add this product to a sale order line, the price that i get through the onchange method
is rounded by the openerp web client, by the class float in openerp/
and that is the price added to the sale_order_line like 12.4400 €. So you cannot work with the web-client if
you've another price accuracy than 2 in the openerp web server. The digit value should be set by a config file,
or better be requestet from openerp server price_accuracy value.
Greets,
Nils Rumprecht
Changed in openobject-client-web: | |
assignee: | nobody → noz (Tiny) (noz-tiny) |
Changed in openobject-addons: | |
assignee: | noz (Tiny) (noz-tiny) → nobody |
Changed in openobject-client-web: | |
status: | In Progress → Fix Committed |
Changed in openobject-client-web: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I am working on a solution for price unit here /code.launchpad .net/~openerp- commiter/ openobject- addons/ chricar_ price_unit
this allows to define arbitrtry price units while retaining the default decimal digits for accountig purpose
https:/