[jira] [Comment Edited] (OFBIZ-6139) Lookup fields break when used with a form having skip-start="true"
[
https://issues.apache.org/jira/browse/OFBIZ-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564549#comment-14564549
]
Pierre Smits edited comment on OFBIZ-6139 at 5/29/15 10:40 AM:
---
Having to have the form name hard coded in the field as in:
{code}
{code}
leads to a degradation in functionality. Such a form can be used only with one
start form.
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 change accordingly.
was (Author: pfm.smits):
Having to have the form name hard coded in the field as in:
{code}
leads to a degradation in functionality. Such a form can be used only with one
start form.
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 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)
[jira] [Comment Edited] (OFBIZ-6139) Lookup fields break when used with a form having skip-start="true"
[
https://issues.apache.org/jira/browse/OFBIZ-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564549#comment-14564549
]
Pierre Smits edited comment on OFBIZ-6139 at 5/29/15 10:39 AM:
---
Having to have the form name hard coded in the field as in:
{code}
leads to a degradation in functionality. Such a form can be used only with one
start form.
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 change accordingly.
was (Author: pfm.smits):
Having to have the form name hard coded in the field as in:
{code}
{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 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)
[jira] [Comment Edited] (OFBIZ-6139) Lookup fields break when used with a form having skip-start="true"
[
https://issues.apache.org/jira/browse/OFBIZ-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564549#comment-14564549
]
Pierre Smits edited comment on OFBIZ-6139 at 5/29/15 10:38 AM:
---
Having to have the form name hard coded in the field as in:
{code}
{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 change accordingly.
was (Author: pfm.smits):
Having to have the form name hard coded in the field as in:
{code}
{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)
[jira] [Comment Edited] (OFBIZ-6139) Lookup fields break when used with a form having skip-start="true"
[
https://issues.apache.org/jira/browse/OFBIZ-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564542#comment-14564542
]
Jacques Le Roux edited comment on OFBIZ-6139 at 5/29/15 10:31 AM:
--
While testing the feature, Pierre Smits wanted to have form-name dynamic by
using {code}form-name="${name}"{code}. Then the form-name attrbute should
support FlexibleStringExpander. This could be another Jira...
was (Author: jacques.le.roux):
While testing the feature, Pierre Smits wanted to have form-name dynamic
{code}(using form-name="${name}"){code}. Then the form-name attrbute should
support FlexibleStringExpander. This could be another Jira...
> 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)
[jira] [Comment Edited] (OFBIZ-6139) Lookup fields break when used with a form having skip-start="true"
[
https://issues.apache.org/jira/browse/OFBIZ-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564542#comment-14564542
]
Jacques Le Roux edited comment on OFBIZ-6139 at 5/29/15 10:30 AM:
--
While testing the feature, Pierre Smits wanted to have form-name dynamic
{code}(using form-name="${name}"){code}. Then the form-name attrbute should
support FlexibleStringExpander. This could be another Jira...
was (Author: jacques.le.roux):
While testing the feature, Pierre Smits wanted to have form-name dynamic (using
form-name="${name}"). Then the form-name attrbute should support
FlexibleStringExpander. This could be another Jira...
> 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)
[jira] [Comment Edited] (OFBIZ-6139) Lookup fields break when used with a form having skip-start="true"
[ https://issues.apache.org/jira/browse/OFBIZ-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354892#comment-14354892 ] Jacques Le Roux edited comment on OFBIZ-6139 at 3/10/15 2:12 PM: - Fixed in trunk r1665535 R14.12 r1665540 R13.07 r1665543+1665560 R12.04 r1665544+1665561 was (Author: jacques.le.roux): Fixed in trunk r1665535 R14.12 r1665540 R13.07 r1665543 R12.04 r1665544 > 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: Bug > 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 lookup > element fixes it. You then need also to set the correct id-name value on > field element. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
