summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/fields/relational_fields.js
diff options
context:
space:
mode:
authorOlivier Dony <odo@odoo.com>2018-05-03 10:49:23 +0200
committerOlivier Dony <odo@odoo.com>2018-05-03 12:17:55 +0200
commit78ce64a6a79a41e673196939f2bb60a44db27f55 (patch)
tree4fab74a6a2c90adcf049d456fe612b21a2681877 /addons/web/static/src/js/fields/relational_fields.js
parent7353405aa4fc88ede6b85bbb46fe0308b17c1052 (diff)
[FIX] account: do not block reconciliation on different partners
This constraint was added during the Great Accounting Reform of v9, in an attempt to help users avoid reconciliation mistakes. It turns out that such mistakes are difficult to make in normal situations, since the system only offers matching entries to reconcile, so the constraint is largely redundant. On the other hand, it does block legit cases of reconciliation, such as those where a large number of lines with different partners are reconciled together. This often happens when reversing a Journal Entry that encompasses multiple customers, such as a POS closing entry, or a manual entry. To make the system more flexible, let's consider that when a manual reconciliation breaks the "single partner" rule explicitly, it's for a good reason, so we should allow it. OPW: 1840437 Backport of 8e73023f689d76dc6d545e617ab1c7ce18334068
Diffstat (limited to 'addons/web/static/src/js/fields/relational_fields.js')
0 files changed, 0 insertions, 0 deletions