We're working with Webi rich client (WRC) r3.1 SP4 FP4.1, and we noticed some strange behaviour.
We have a report with 2 dataproviders based on the same universe, which have a year dimension in common (exact same name, same datatype). It is not the same year-object.
We expected that WRC would auto-merge those 2 year objects, but it doesn't and we're wondering what might be the cause.
Thanks for your help
We've done some further investigation in other Fora and on several Blogs. Based on that input we're looking for confirmation that you can only auto-merge on the exact same object from the same universe.
This would mean that auto-merge does not work on dataproviders based on different universes but containing "mergeable" data.
Can anyone confirm the above?
No, not at all, you are not limited to one universe!
the whole point of this functionality is to merge together different data providers (queries) into a synchronised level of granularity into the report. this has to be done on a common dimension.
The user documentation is very clear about the use-cases: http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_ia_en.pdf
As mentioned in my initial post, we're on BOXI 3.1 SP4 FP4.1.
What you are describing is the principal of "manual" merging, my question is related to the automatic merging.
I would like to know this, because we're having problems working out a working example for drilling in Webi using query drill with multiple dataproviders and merged dimensions. And we're assuming that the drilling accross the multiple dataproviders is only possible when automerge is active. Because all dataproviders need changes is the where clause of the queries to limit the scope of analysis during the drilling.
I think you need to contact support, log an OSS, and walk them through this via screenshare. We can also connect remotely to your database and consume your data so that we can discuss 'in context'
I know there have been some minor changes in Merge behaviour, but i thought these were for bi 4.0.
That said, perhaps you are being impacted by an regression, given your build history. (i..e using the latest, seeing a change in behaviour)
Best of luck going forward.