Re: Complex relations in View Entity defs

[David E Jones <de...@me.com>]

There hasn't been a lot of interest in that feature, so it isn't totally implemented.

Basically don't use the entity-alias attribute on the condition-expr element, and make sure the field-name matches an alias on the view-entity (ie to do a condition on a field it must be aliased for now).

-David


On Apr 28, 2011, at 7:02 AM, Justin Robinson wrote:

> Ok I found a ref in a bug report on ofbiz from 2009
> 
> <entity-condition>
> <condition-list>
> <condition-expr entity-alias="PPC" field-name="inputParamEnumId"
> operator="equals" value="PRIP_QUANTITY"/>
> <condition-expr entity-alias="PPC" field-name="operatorEnumId"
> operator="equals" value="PRC_GTE"/>
> </condition-list>
> </entity-condition>
> 
> Using entity-condition in the view entity def, but I'm still unclear
> as to how I can get a list of attrName & attrValue fields to appear as
> field & values respectively in a view entity....
> 
> Can anyone help me out or point me in the direction of more info on the topic?
> 
> 
> On Thu, Apr 28, 2011 at 3:23 PM, Justin Robinson
> <ju...@venturenet.co.za> wrote:
>> I'm creating a new view entity that has to contain several different
>> attribute records from the same table.
>> Attributes are distinguished by a combination on an id and the
>> attrName. I've used a combination of fields for a view link, in
>> another case, before like so:
>> 
>> <view-link entity-alias="SUB" rel-entity-alias="OI" rel-optional="true">
>>            <key-map field-name="orderId" rel-field-name="orderId"/>
>>            <key-map field-name="orderItemSeqId"
>> rel-field-name="orderItemSeqId"/>
>> </view-link>
>> 
>> What I'd like to know is, is it possible to have like a
>> 'rel-field-value' type thing where I could specify the attrName
>> instead of a rel-field-name?
>> Then the other thing is, when I was creating other views entities, I
>> found you can't relate to the same entity twice in the same view
>> entity even if you def it twice with 2 alias, I worked around this by
>> creating a new view entity the joined the first one but there must be
>> another way around this, else will I have to create a new view entity
>> the relates to the last one for each attribute I add?
>> 
>> --
>> Regards,
>> Justin
>> Venture-Net Research & Development
>> 
> 
> 
> 
> -- 
> Regards,
> Justin
> Venture-Net Research & Development