[
https://issues.apache.org/jira/browse/OFBIZ-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564549#comment-14564549 ]
Pierre Smits commented on OFBIZ-6139:
-------------------------------------
Having to have the form name hard coded in the field as in:
{code}
<form name="RequestItemProduct" type="single" skip-start="true" skip-end="true">
<field name="productId" title="${uiLabelMap.CommonProduct}">
<lookup target-form-name="LookupProduct" description-field-name="productName" show-description="false"/>
</field>
<field name="productName" form-name="EditCustRequestItem" position="2"><text read-only="true"/></field>
<field name="quantity" title="${uiLabelMap.CommonQuantity}"><text size="10"/></field>
</form>
{code}
leads to a degradation in functionality.
With dynamic form building whereby the start-form might be conditionally defined (based on parameter values), the form name required in the lookup fields of the injectable sub-forms should be change accordingly.
> Lookup fields break when used with a form having skip-start="true"
> ------------------------------------------------------------------
>
> Key: OFBIZ-6139
> URL:
https://issues.apache.org/jira/browse/OFBIZ-6139> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
> Affects Versions: Trunk
> Reporter: Jacques Le Roux
> Assignee: Jacques Le Roux
> Priority: Minor
> Labels: lookup
> Fix For: 14.12.01, 12.04.06, 13.07.02, Upcoming Branch
>
>
> We neglected this aspect so far. Adding a "form-name" attribute to the field element of the lookup fixes it.
> The value of "form-name" attribute must be the name of the "parent form", ie the 1st form (the one with skip-end="true") which precedes the current form (which has skip-start="true").
> If you use a related description field (using the "description-field-name" attribute of the lookup element) you need to put the "form-name" attribute in this field element too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
