2019 Mar 18 8:13 AM
Hi everyone,
We are developing Multi-Target Applications (MTAs) in WebIDE FullStack to be deployed in the Cloud Foundry environment. Those MTAs have a DB module with calculation views(CVs), A Node.JS module to expose those calculation views as odata services and HTML5 modules for UI5 apps using the Fiori Elements templates.
We have CVs for Header and Item data, and those data are exposed as different Entity types on the odata, with a navigation property linking them.
Header (Product table - Shows the different products on an invoice)Item (Charges table - Shows the different charges applied to the product)
The problem is that the client is requiring to see both Header and Item data on the same Analytical Page. We made it work by creating a single CV combining both data.
Combined
However I am currently struggling with the aggregation. Because the relation between Header and Item is 1:n, Cost and Weight will be duplicated for every Item entry on a particular Header. Therefore, when I make the aggregation of the whole thing, their values will be way higher than they should.
So my question is: is there a way for making the calculation view recognise the hierarchy levels between data sources and keep them from aggregating in such cases? I know when you create a Counter on the CV, you can set which properties to take into account. Is there a similar feature for other Measure properties?
Best regards,
André
Hi everyone,
We are developing Multi-Target Applications (MTAs) in WebIDE FullStack to be deployed in the Cloud Foundry environment. Those MTAs have a DB module with calculation views(CVs), A Node.JS module to expose those calculation views as odata services and HTML5 modules for UI5 apps using the Fiori Elements templates.
We have CVs for Header and Item data, and those data are exposed as different Entity types on the odata, with a navigation property linking them.
Header (Product table - Shows the different products on an invoice)Item (Charges table - Shows the different charges applied to the product)
The problem is that the client is requiring to see both Header and Item data on the same Analytical Page. We made it work by creating a single CV combining both data.
Combined
However I am currently struggling with the aggregation. Because the relation between Header and Item is 1:n, Cost and Weight will be duplicated for every Item entry on a particular Header. Therefore, when I make the aggregation of the whole thing, their values will be way higher than they should.
So my question is: is there a way for making the calculation view recognise the hierarchy levels between data sources and keep them from aggregating in such cases? I know when you create a Counter on the CV, you can set which properties to take into account. Is there a similar feature for other Measure properties?
Best regards,
André
2019 Mar 18 8:17 AM
2019 Mar 18 10:37 AM
2019 Mar 18 3:00 PM