summaryrefslogtreecommitdiff
path: root/doc/reference/javascript_reference.rst
diff options
context:
space:
mode:
authorNans Lefebvre <len@odoo.com>2019-09-24 17:06:30 +0000
committerfw-bot <otis@odoo.com>2019-10-10 11:11:30 +0000
commitd77a8de5f9a53486337682ce8c7b79317cfe98ab (patch)
tree420ffaa21d14218c2f6da4b367dd190a6538cba6 /doc/reference/javascript_reference.rst
parent398592fb9ded46f28a7b2a6e210b7000d6e30dcd (diff)
[FIX] account: round debit and credit of account move lines at creation
This fix is similar to 8020033; both are workarounds for the bug (limitation) introduced by 9d87d15db6dd40a5a0162fb126c725a2f0a40414. In this case, the currency_field is a related field, and these fields are only computed after scalar values are written in database. As a result, this value is not rounded at creation. It is a problem since typically accounting reports are written directly in SQL, and thus reuse the values directly. Anyway even in the ORM the convert_to_cache optimised this away using the assumption that 'the value should have been rounded in convert_to_column'. It follows that in the report, errors can be accumulated to the point where the report is not balanced. This needs to be fixed in database by going through every existing line. Of note: the limitation that was readily acknowledged has not been worked around anywhere, in fact almost every single currency_field is a related one. Also of note, commit afef71d6b should "Always round monetary values in database" while it explicitly checked for the presence of the currency_field in the values and while not introducing a mechanism to make sure it would always be in the values. opw 2066849 closes odoo/odoo#38376 X-original-commit: 937893379ba8c149c681b61a951ca507df798e6b Signed-off-by: Nans Lefebvre (len) <len@odoo.com>
Diffstat (limited to 'doc/reference/javascript_reference.rst')
0 files changed, 0 insertions, 0 deletions