From 59ad76c21e385eab807fae96dd15e748835366de Mon Sep 17 00:00:00 2001 From: Mihir Kandoi Date: Wed, 17 Jun 2026 16:08:24 +0530 Subject: [PATCH] fix(postgres): satisfy strict GROUP BY in asset depreciation query Co-Authored-By: Claude Opus 4.8 (1M context) --- erpnext/assets/doctype/asset/depreciation.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/erpnext/assets/doctype/asset/depreciation.py b/erpnext/assets/doctype/asset/depreciation.py index fe0710730d4..762ed796056 100644 --- a/erpnext/assets/doctype/asset/depreciation.py +++ b/erpnext/assets/doctype/asset/depreciation.py @@ -96,7 +96,9 @@ def get_depreciable_assets_data(date): .where(a.status.isin(["Submitted", "Partially Depreciated"])) .where(ds.journal_entry.isnull()) .where(ds.schedule_date <= date) - .groupby(ads.name) + # a.name/a.creation are constant per ads.name; include them so postgres accepts the + # SELECT and ORDER BY (one row per Asset Depreciation Schedule either way) + .groupby(ads.name, a.name, a.creation) .orderby(a.creation, order=Order.desc) )