You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2019/05/26 08:02:00 UTC

[jira] [Commented] (OFBIZ-11069) Add coalesce to aggregate-function of model view

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

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

HI Jinghai,

Sounds good to me: +1

> 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)