[ 
https://issues.apache.org/jira/browse/OFBIZ-11179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leila Mekika updated OFBIZ-11179:
---------------------------------
    Attachment:     (was: ExampleWithKeyMap.xml)

> Change current view-link requirement to allow use of  entity-condition only 
> in view-entities
> --------------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-11179
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-11179
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: ALL COMPONENTS
>    Affects Versions: Trunk
>            Reporter: Leila Mekika
>            Priority: Minor
>         Attachments: ExampleWithoutKeyMap.xml, OFBIZ-11179.patch
>
>
> To explain the subject, i will give an example encountered recently:
> We used, for a customer project, a view with Agreement, Virtual and Variant 
> product entities and where the agreement can be attached to a virtual OR a 
> variant product.
>  So to make a view returning Variant Product, Virtual Product AND Agreement 
> informations, i could not create a view, as the key-map link is mandatory and 
> made it impossible.
> I can not have an alternative relation to the same entity so we have to 
> duplicate member-entity and an alternative relation path (see attached file 
> ExampleWithKeyMap.xml)
>  And as the coalesce is not an existing function, it require to update the 
> framework. The result is a complicated and ugly entity-view
> I think this can have been much simpler if i could have done it directly 
> through the entity-condition (see the AGPA/PDTA view link in attached file 
> ExampleWithoutKeyMap.xml)
> So the purpose of this jira is to add the possibility to create a view-link 
> without key map,  if there is an entity-condition.
> You can test by applying the given patch and add the entity view from 
> attached file ExampleWithoutKeyMap.xml



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to