[ 
https://issues.apache.org/jira/browse/OFBIZ-11069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16848375#comment-16848375
 ] 

Jacques Le Roux commented on OFBIZ-11069:
-----------------------------------------

Pierre,

You say above:
bq. . I have looked at the various entities, but there is no such 
'skuProductId' field in the model. Is this intentional? Or just a prelude to 
have the field introduced into the Product entity?

In the description Jinghai explained:
bq. When building operation/inventory reports, to be compatible with previous 
implement, *I have to merge the sku product Id column into the productId 
column*, so comes the coalesce patch. 

> Add coalesce to aggregate-function of model view
> ------------------------------------------------
>
>                 Key: OFBIZ-11069
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-11069
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: framework
>            Reporter: Shi Jinghai
>            Priority: Trivial
>              Labels: IoT, ModelViewEntity
>             Fix For: Trunk
>
>         Attachments: ModelViewEntity-function-coalesce.patch
>
>
> While in our IoT case, a product may have a sku product id as well as a 
> productId (product instance) by identified from unique id i.e. an EPC.
> When building operation/inventory reports, to be compatible with previous 
> implement, I have to merge the sku product Id column into the productId 
> column, so comes the coalesce patch. 
> The usage example:
> {code:java}
> <alias entity-alias="IID" name="productId" group-by="true" 
> function="coalesce">
>     <complex-alias operator=",">
>         <complex-alias-field entity-alias="IID" field="skuProductId"/>
>         <complex-alias-field entity-alias="IID" field="productId"/>
>     </complex-alias>
> </alias>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to