Hi Aayush,
just few days ago I have done something similar to what you describe and
submitted a patch into https://issues.apache.org/jira/browse/OFBIZ-3902

I submitted the code and not committed because it is not yet finished but
may with your help we can get all done.

-Bruno

2010/8/29 Aayush <aayush...@gmail.com>

>
> i was trying to do this but i was facing problems ...
> now since the ftl was performing 2 tasks
> 1. Search Options
> 2. Search Results
> so in order to converting it into form-widget i made 2 forms
>
> 1. FindParty -for  Search Options
> 2. ListParties -for Search Results
>
> i am done with the 1st form but i am facing some problems with the 2nd
> the problem in 2nd form is
> that i'v made 2 fields like this
>
> <field name="partyId" title="${uiLabelMap.PartyPartyId}" >
>     <hyperlink also-hidden="false" description="${partyId}"
> target="viewprofile">
>          <parameter param-name="partyId"/>
>      </hyperlink>
> </field>
>
> and
>
> <field name="partyId" title="${uiLabelMap.PartyName}"><display-entity
> entity-name="Person"/></field>
>
> Entity for the 1st field is "Party" and
> for 2nd is "Person"
>
> now as the name of both the fields is same ("partyId ") so the 2nd one is
> replacing the first
> i.e. on the browser only PartyName is getting displayed ...
>
> if i am deleting the 2nd line (i.e. 2nd field fully) then it is displaying
> PartyPartyId on the browser
> so i think the problem is in the field name ...
> and it is necessary for me to mention the same field name
> in order to bring data from the Entity
> because the name of the fields should be the primary key of the entity and
> they are same for both Party as well as Person...
>
> so please suggest me how to solve this problem
> i am very close
> i want to make exactly the same page as it comes out by findparty.ftl
>
> --
> View this message in context:
> http://ofbiz.135035.n4.nabble.com/problems-in-converting-findparty-ftl-into-form-widget-tp2399128p2399128.html
> Sent from the OFBiz - Dev mailing list archive at Nabble.com.
>

Reply via email to