[
https://issues.apache.org/jira/browse/OFBIZ-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797999#comment-13797999
]
Christian Carlow edited comment on OFBIZ-5356 at 10/17/13 3:24 PM:
-------------------------------------------------------------------
The concatenated string of primary keys is blank when referenced in
LookupForms.xml for the listLookupOrderItem form I created so I had to
construct it again in the field definition:
<field name="orderItemId" widget-style="buttontext">
<hyperlink target-type="plain" also-hidden="true"
description="${orderId}\_pk_${orderItemSeqId}"
target="javascript:set_value('${orderId}\_pk_${orderItemSeqId}')"/>
</field>
The concatenated orderItemId field is not blank for the Lookup drop down list.
I don't understand what causes it to be blank for the form widget.
was (Author: ofbizzer):
The concatenated string of primary keys is blank when referenced in
LookupForms.xml for the listLookupOrderItem form I created so I had to
construct it again in the field definition:
<field name="orderItemId" widget-style="buttontext">
<hyperlink target-type="plain" also-hidden="true"
description="${orderId}_pk_${orderItemSeqId}"
target="javascript:set_value('${orderId}\_pk_${orderItemSeqId}')"/>
</field>
The concatenated orderItemId field is not blank for the Lookup drop down list.
I don't understand what causes it to be blank for the form widget.
> Ability to select Lookup records having more than one primary key field
> -----------------------------------------------------------------------
>
> Key: OFBIZ-5356
> URL: https://issues.apache.org/jira/browse/OFBIZ-5356
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
> Affects Versions: Release Branch 12.04
> Reporter: Christian Carlow
> Fix For: Release Branch 12.04
>
>
> Having the ability to select a record from Lookup records containing more
> than one primary-key field would be quite useful.
> I have the need to select a single OrderItem from a list of OrderItems
> associated with more than one OrderHeader. I also need to be able to select
> a single ShipmentItem from a list containing multiple Shipments.
> Having single field primary keys for these tables would provide a solution
> but would entail a lot of work to make the system use the new primary keys.
> Another way would be to allow for Lookup controls the ability to have
> multiple keys associated with them.
> Either way, seems like a lot of work to make this happen.
> Anyone have a different solution?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
