[ https://issues.apache.org/jira/browse/OFBIZ-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564599#comment-14564599 ]
Pierre Smits commented on OFBIZ-6429: ------------------------------------- This also applies when the start form uses an alt-target setting, as in e.g.: {code} <form name="EditVendor" type="single" target="updateVendor" title="" default-map-name="vendor"> <actions> <entity-one entity-name="Vendor" value-field="vendor"/> </actions> <alt-target use-when="partyId==null" target="createVendor"/> <alt-target use-when="partyId!=null&&vendor!=null" target="updateVendor"/> ..... </form> {code} > For lookup fields in sub forms (skip-start + skip-end), the value of the > form-name attribute should be dynamically rendered > --------------------------------------------------------------------------------------------------------------------------- > > Key: OFBIZ-6429 > URL: https://issues.apache.org/jira/browse/OFBIZ-6429 > Project: OFBiz > Issue Type: Sub-task > Components: framework > Affects Versions: Trunk > Reporter: Pierre Smits > Labels: dynamic, forms > Fix For: Upcoming Branch > > > The solution in OFBIZ-6139 means hard-codedness of the value of the form-name > attribute of a field. > As shown in following example: > {code} > <form name="RequestItemProduct" type="single" skip-start="true" > skip-end="true"> > <field name="productId" title="${uiLabelMap.CommonProduct}" > form-name="EditCustRequestItem"> > <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} > However when the start form changes based on conditions in the screen > (parameters, etc), the lookup field won't work due to this hard-codedness. -- This message was sent by Atlassian JIRA (v6.3.4#6332)