XIR3 upgrade -Merged Dimensions and other #multivalue issues

building reports webintelligence
1

I was wondering if anyone else has experienced report conversion problems after upgrading to XIR3 ? …specifically regarding Merged Dimension functionality. I use a lot of variables to conditionally select what I need when multiple values exist (like qtys by year) and in new XIR3 reports I could no longer use some variables as they only gave me #multivalue result (and no, using min or max did not resolve this). I ended up having to break my single query up into separate ones to avoid the multiple values (ie: year) which in my estimate is going backwards in functionality and response time. If anyone has found a proper solution, I’d LOVE to know!

There have been other changes too now requiring use of In Section, In Report, NoFilter, etc where previously not needed :frowning:

These changes were not reported as planned nor expected by us for conversion time required, so please check your reports after upgrading!

mdower (BOB member since 2009-02-27)

2

I first encountered this problem with XIR1, after which it got fixed in XIR2. to my surprise the error now occurs again in several XIR3 environments I’ve been working on !

I’m hoping to be in a position to install a hotfix soon, and curious to see if this issue was addressed … will keep you posted.

mirko (BOB member since 2002-08-21)

3

may be you can use sum(…)

paidichina (BOB member since 2009-08-18)

4

this is not an option, since the error even occurs when none of the columns contains numerical data …

take these 3 columns: , , , where the #MULTIVALUE error appears in the last column ().

now where would you use sum() … :wink:

other thread suggest the use of max() to work around this issue, but I need to display ALL product numbers for each client, not the one with max value !

mirko (BOB member since 2002-08-21)

5

What migration path did you take?

There were changes to the calculation engine in XIr2 SP2, I would suggest that this works the same way in 3.0.

Also, are you Merging or Extending Merged Dimensions?

Mak 1 :uk: (BOB member since 2005-01-06)

6

I’m afraid I may have responded to the wrong thread, since the #MULTIVALUE errors I’ve been dealing with are not related to migration at all: they appear in newly created WebI reports.

mirko (BOB member since 2002-08-21)

7

Can you elaborate with your example a bit more?

What you are merging on, queries e.t.c?

Also, my question regarding merged and extended dimensions still applies…:slight_smile:

Mak 1 :uk: (BOB member since 2005-01-06)

8

I’m currently looking at a report where the problem occurs even though it contains only 1 dataprovider, so no merging at all …

mirko (BOB member since 2002-08-21)

9

The wya you have formatted your field names it looks like Deski syntax, not Webi… :? .

So all these columns are dimensions displayed in a simple table.

Are they character type?

Does this happen with all your dimnsion objects?

Mak 1 :uk: (BOB member since 2005-01-06)