[
https://issues.apache.org/jira/browse/OFBIZ-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Carlow updated OFBIZ-5916:
------------------------------------
Attachment: OFBIZ-5916-2.patch
This is a revised patch that uses the new from().where().orderBy() methods
which prevents the need for EntityCondition imports. For future patches, is it
worth making an effort to change any delegator.find methods with the new ones?
> Cutting List Report from Manufacturing Shipment Plans throws error due to due
> to missing EntityCondition import
> ---------------------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-5916
> URL: https://issues.apache.org/jira/browse/OFBIZ-5916
> Project: OFBiz
> Issue Type: Bug
> Components: manufacturing
> Affects Versions: Trunk
> Reporter: Christian Carlow
> Priority: Minor
> Attachments: OFBIZ-5916-2.patch, OFBIZ-5916.patch
>
>
> This error occurs when clicking the "Cutting List Report" button from the
> Manufacturing -> Shipment Plans page once a production run has been created
> for a planned shipment:
> Error running script at location
> [component://manufacturing/webapp/manufacturing/WEB-INF/actions/reports/ShipmentWorkEffortTasks.groovy]:
> groovy.lang.MissingPropertyException: No such property: records for class:
> ShipmentWorkEffortTasks
> To reproduce:
> 1. Create a shipment with status Schedued and a planned item
> 2. Navigate to Manufacturing -> Shipment Plans and click "Create Production
> Runs" for the shipment
> 3. Click the "Cutting List Report" button that appears once Production Runs
> have been created
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
