I have a QaaWS connection and as of now , It has 1 dimension & 4 measures. All measures have SUM() in select and also SUM at projection level in universe.
Now I have to add 2 more measures which are already there in the universe -
Both the objects have SUM in projection but not in SELECT. Due to which, the values are not getting aggregated in QaaWS output and it is leading to the massive data in Xcelsius dashboard and failing.
Can someone please guide me what solution I can try here to over come this issue?
Decision makers… … I am tired of telling them, don’t know what had gone into their mind and they just want to use QaaWS… :x :x :x and not at all ready to go for BIWS
And due to this, we are facing issues related to aggregation…
Actually the requirement says - That we have to use the code without SUM in Select and this is how WEBI report is build. Now the data in WEBI and DASHBOARD needs to be in sync.
So I cannot change the existing Object, I can get one more added if it solves the problem, but Mak is right, it won’t solve.
Now I am thinking if the same logic can be put in DB or some solution can be worked out at DB level, so that I can get the field in universe and use the same in QaaWS with other measures objects…
I suspect that the issue lies with the granularity, i.e. if A*B is summed it will produce the wrong result?
If that is the case then, I would imagine, the data is not modelled correctly.
Not sure, I have just got into this project and A*B is definately not giving wrong results or you can say this is what Client is liking…
And now same thing needs to be replicated in the dashboard. I guess we would need to see if something can be done at ETL level or else… For sure as of now, I don’t know.
Well, it looks like it is performing the multiplication at a transaction level, so I would expect the results to be currently correct (data quality withstanding)
(BOB member since 2007-10-05)
(BOB member since 2002-06-20)
.