From 51930641c5c5853e2c2fda80098a1e3bac20dfd0 Mon Sep 17 00:00:00 2001 From: Jacques Le Roux Date: Mon, 31 Jan 2022 12:21:37 +0100 Subject: [PATCH] Fixed: Wrong Field Name Definition in RequirementForms (OFBIZ-12505) The issue exists also in the older version. The field "requirementByDate" form "FindApprovedProductRequirements" in RequirementForms.xml has been set wrongly and it should be "requiredByDate". This causes the result could not be queried out properly as indicated as below: The result is governed by the service "getRequirementsForSupplier", where reads the list from the view "RequirementAndRole". In the view entity definition, the field is defined as , but it is not the case in the form "FindApprovedProductRequirements" above. After changing it to the correct name, the bug is solved. jleroux: Same exists in OrderEntryForms::FindRequirements Thanks: Schumann Ye for report Pierre Smits for creating the initial PR494 --- applications/order/widget/ordermgr/OrderEntryForms.xml | 2 +- applications/order/widget/ordermgr/RequirementForms.xml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/applications/order/widget/ordermgr/OrderEntryForms.xml b/applications/order/widget/ordermgr/OrderEntryForms.xml index f46badd7a6..90d60a55b1 100644 --- a/applications/order/widget/ordermgr/OrderEntryForms.xml +++ b/applications/order/widget/ordermgr/OrderEntryForms.xml @@ -24,7 +24,7 @@ under the License. - +
- +