From 38955af802197cf1a49b63a0dbb2e1decc730cfb Mon Sep 17 00:00:00 2001 From: Sanket Shah <113279972+Sanket322@users.noreply.github.com> Date: Wed, 12 Mar 2025 22:37:08 +0530 Subject: [PATCH] fix: using `in` for lookup in list instead of directly assigning (#46492) fix: using in for lookup in list instead of assigning Co-authored-by: Sanket322 --- .../accounts/report/accounts_receivable/accounts_receivable.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/erpnext/accounts/report/accounts_receivable/accounts_receivable.py b/erpnext/accounts/report/accounts_receivable/accounts_receivable.py index c7df618dd6a..482fdada06b 100644 --- a/erpnext/accounts/report/accounts_receivable/accounts_receivable.py +++ b/erpnext/accounts/report/accounts_receivable/accounts_receivable.py @@ -733,7 +733,8 @@ class ReceivablePayableReport: for party_type in self.party_type: party_field = scrub(party_type) if self.filters.get(party_field): - or_filters.update({party_field: self.filters.get(party_field)}) + or_filters.update({party_field: ["in", self.filters.get(party_field)]}) + self.return_entries = frappe._dict( frappe.get_all( doctype, filters=filters, or_filters=or_filters, fields=["name", "return_against"], as_list=1