diff options
| author | Florian Gilbert <flg@odoo.com> | 2020-07-30 07:47:39 +0000 |
|---|---|---|
| committer | Florian Gilbert <flg@odoo.com> | 2020-08-10 08:59:45 +0000 |
| commit | 3a0e36475811f1c68a20ae0e86ac0b3691015df2 (patch) | |
| tree | fc1695ae99bcb5f4f2308a99ff696abd6c1bda6c /addons/web/static/src/js/fields/basic_fields.js | |
| parent | 1e2e0f663efac81ad480f5ff06a61c4265e28227 (diff) | |
[FIX] account: Order move for hash & add security check for resequence
Order move for hash: In the method write, we sort the recordset following this rule: by date, by ref and by id.
This rule is used because we need to be consistent with the method _compute_name.
If we don't filter moves like that, we could possibly have a problem.
If you have several moves and you post them at the same moment with the action "Post entries", the hash sequence
could be in another order than the name sequence.
For example:
Move_20 (29/07/2020) - Hash_2
Move_21 (02/07/2020) - Hash_1
About security check, if the hash is activated, the user cannot reorder by date with resequence
because we don't want that the name sequence have not the same order than hash sequence.
Task ID: 2297407
closes odoo/odoo#55669
X-original-commit: b3ae96dc52178a3b13dda845244fe34268aed8a0
Signed-off-by: Cedric Snauwaert (csn) <csn@openerp.com>
Diffstat (limited to 'addons/web/static/src/js/fields/basic_fields.js')
0 files changed, 0 insertions, 0 deletions