[
https://issues.apache.org/jira/browse/OFBIZ-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889550#comment-13889550 ]
Leon commented on OFBIZ-5481:
-----------------------------
hi, Jacques,
I found the reason: the 'specialpurpose' component "scrum" is disabled in our environment.
Is that better to move the FK relationship definition to same place where its field is defined? In this case, the foreign key from "parentCustRequestId"to custRequestId is defined within order component but the field "parentCustRequestId" itself is defined in "scrum".
> [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
