This issue looks like an issue of Python, sometimes when saving a value as FLOAT, when you read the data, it will be a little off. So this can be fixed using another way of saving data.
If the field is one of a default module, you have to create your own module, and convert the value yourself. When the field is part of a module downloaded from internet or made by you, you can change/modify that code or create another module to fix this behaviour.
It might be a good idea as well to fill in a bug-report. This can be done at https://bugs.launchpad.net/openobject-addons/+filebug
Please try to give a substantial answer. If you wanted to comment on the question or answer, just use the commenting tool. Please remember that you can always revise your answers - no need to answer the same question twice. Also, please don't forget to vote - it really helps to select the best questions and answers!
About This Community
|Asked: 7/5/13, 5:07 AM|
|Seen: 617 times|
|Last updated: 3/16/15, 8:10 AM|