[
https://issues.apache.org/jira/browse/OFBIZ-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889644#comment-13889644 ]
Jacques Le Roux commented on OFBIZ-5481:
----------------------------------------
Yes I see no issues doing that, actually even instead of using an entity extension we could put the new fields in the original entity. I don't know why it was done this way, apart maybe to keep scrum changes located. Since it could be cumbersome in a release if we do that we should put a comment about these fields only used (for now) in the scrum component.
Other opinions?
> [RelationFieldNotFound] warining during startup : parentCustRequestId of entity CustRequest is not found.
> ---------------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-5481
> URL:
https://issues.apache.org/jira/browse/OFBIZ-5481> Project: OFBiz
> Issue Type: Bug
> Components: order
> Affects Versions: SVN trunk
> Reporter: Leon
> Priority: Minor
>
> {quote}
> [ GenericDelegator.java:243:WARN ] [RelationFieldNotFound] The field parentCustRequestId was specified in the keymaps but is not found for relation ParentCustRequest of entity CustRequest.
> [ GenericDelegator.java:243:WARN ] [RelationRelatedFieldNotFound] The field "parentCustRequestId" of related entity CustRequest was specified in the keymaps but is not found for relation ChildCustRequest of entity CustRequest.
> {quote}
> Entity CustRequest misses field parentCustRequestId, or unnecessary foreign key "CUST_REQ_PARENT"?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
Locked
