From 9499b5d4d2481f79226ddbcf1e66176ce216b6fc Mon Sep 17 00:00:00 2001 From: Joren Van Onder Date: Fri, 27 May 2016 13:10:18 +0200 Subject: [PATCH] [FIX] account_asset: use newest depreciation date for new depreciations The code uses self.depreciation_line_ids[0] and incorrectly assumes it is always the latest (newest) depreciation line. This sorts the recordset to guarantee that this is true. opw-678678 --- addons/account_asset/account_asset.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/addons/account_asset/account_asset.py b/addons/account_asset/account_asset.py index 7e53f0ff4c1..aef5666277c 100644 --- a/addons/account_asset/account_asset.py +++ b/addons/account_asset/account_asset.py @@ -160,7 +160,7 @@ class AccountAssetAsset(models.Model): def compute_depreciation_board(self): self.ensure_one() - posted_depreciation_line_ids = self.depreciation_line_ids.filtered(lambda x: x.move_check) + posted_depreciation_line_ids = self.depreciation_line_ids.filtered(lambda x: x.move_check).sorted(key=lambda l: l.depreciation_date, reverse=True) unposted_depreciation_line_ids = self.depreciation_line_ids.filtered(lambda x: not x.move_check) # Remove old unposted depreciation lines. We cannot use unlink() with One2many field