[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=16848557#comment-16848557
]
Shi Jinghai commented on OFBIZ-11069:
-
Hi Jacques and Pierre,
Thanks for the comments and votes!
On the example of sku and product instance, it's more and more common in our
life, a product has one or two identity code, for example, a mobile has one or
two IMEI, a computor has a Serial Number, a car has an engine code and a
VIN(Vehicle Identification Number), a cloth has a RFID and etc. If no
objection, I'll create a new Jira on this topic.
> 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}
> function="coalesce">
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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=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}
> function="coalesce">
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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=16848365#comment-16848365
]
Pierre Smits commented on OFBIZ-11069:
--
Hi Jinghai,
+1 on introducing the coalesce functionality.
In the example provided you're talking about the skuProductId field coming from
the same entity as the productId. 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?
> 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}
> function="coalesce">
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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}
> function="coalesce">
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
