diff options
| author | Martin Trigaux <mat@odoo.com> | 2017-05-08 11:37:54 +0200 |
|---|---|---|
| committer | Martin Trigaux <mat@odoo.com> | 2017-05-08 16:56:36 +0200 |
| commit | 7afe6d28b6eea2d2ca20b491afd2fb46dbea5615 (patch) | |
| tree | aab6d5df77283e172b515b785a7edc18a9a46b5f /addons/web/static/src/less/fields.less | |
| parent | 47dab7d3b4aae8cbb29c56b695ba270c8f6923b4 (diff) | |
[FIX] account: do not display unused field
The field move_line_ids was present in the view and used only for display
purposes. However modifying another field triggering an onchange (e.g. a payment
line) was recreating the move lines.
Recreating the accounting entries may trigger an error if the entries are
already posted.
The entries are recreated because:
1. the move_line_ids is loaded with the default tree & form view for
account.move.line records, displaying several fields
2. some of the fields (e.g. reconciled) are computed
3. the initial onchange recomputes all the computed field, including the one
on the one2many (e.g. recomputing move_line_ids.reconciled)
4. the field being dirty, the onchange returns the value of move_line_ids with
[(5,),(1,id,{...}),...]
5. trying to save the modified lines may fail
Replace the field by a simple readonly integer field.
opw-741205
Diffstat (limited to 'addons/web/static/src/less/fields.less')
0 files changed, 0 insertions, 0 deletions
