[
https://issues.apache.org/jira/browse/OFBIZ-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327605#comment-15327605
]
Amardeep Singh Jhajj commented on OFBIZ-7335:
---------------------------------------------
While working on this issue, I found that the fromDate for party assignment is
set using WorkEffort's estimatedStartDate. IMO, fromDate should also be a part
of party assignment create form, because if we are going to expire and create
new record of party assignment then there can be case of duplicate key error. I
tried using the same partyId, workEffortId and roleTypeId, i got the duplicate
key error. The reason of error is fromDate which was set from
estimatedStartDate. So, fromDate should always be different when creating party
assignment.
I have created a new ticket (OFBIZ-7336) for adding fromDate and thruDate to
the Production Run "Add Party" form.
> Production run party assignment's thruDate should be editable
> -------------------------------------------------------------
>
> Key: OFBIZ-7335
> URL: https://issues.apache.org/jira/browse/OFBIZ-7335
> Project: OFBiz
> Issue Type: Improvement
> Components: manufacturing
> Affects Versions: Trunk
> Reporter: Amardeep Singh Jhajj
> Assignee: Amardeep Singh Jhajj
> Attachments: OFBIZ-7335.patch
>
>
> Currently, we don't have support to set thruDate for production run party
> assignment. So, there should be a support of setting the thruDate if needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
