I know that most of you are aware of the term “Fully qualified member names” in Essbase. For those who are not go through MDX Syntax for Specifying Duplicate Member Names and Aliases.
There was a question raised by Martin S on network54 saying that he is seeing that member names are appearing with square brackets and periods. (The way how a duplicate member is referenced, name enclosed in square brackets([]) and separated by a period.)
My first response was “Are you having duplicate members in your outline?”. After posting the answer (question actually) I went back and checked Sample Basic to see what he is talking about.
To my surprise what Martin S is seeing is indeed a weird behavior. Let’s see what it is.
Smart View retrieval from Sample Basic application. Nothing strange here. So the next step was to perform a member selection operation on Product. (The reason why Product is selected – well I know there is an alternate hierarchy)
Nothing strange here. Now let’s change the alias to None.
Let’s do the member selection again.
Oh yes, the alternate hierarchy is now represented as a fully qualified name.
What happens if I use those members in a report?
Will I get the correct numbers?
If you answered “Yes”, you lost 1 Million Dollar 🙂
The retrieval was done by removing “Preserve Formulas and Comments in ad hoc operations (except pivot)”. (When it is “ON” Smart View interprets those members as comments).
Tim Tow pointed out that The code in 11.1.2.3 is returning TRUE for IEssMemberCell.isNonUnique() method whereas in earlier versions of Essbase it returned false. (I believe him, he is Mr. API 🙂 )
I tested the same on 11.1.2.2.000 Essbase and Smart View 11.1.2.2.310 and 11.1.2.2.000 and both returned the same results (alternate were represented as fully qualified).
If you are using an earlier version of Essbase and Smart View (pre 11.1.2.2) I would love to know the results.
Hey!
I just noticed this error this morning (and did have to play the fun game with the client of…are you sure??)
Choosing to render Member name AND alias seems to fix the problem (albeit with rendering both the member name and alias!)
Does anyone know if a ticket has been raised for this?
@peter I'm planning to raise one
G'day Celvin,
beat you too it – walked oracle support through it and it's been replicated at their end.
Bug 17280541 has been created.
Interestingly it has to have come through in one of the later essbase patches as it doesn't exist in 11.1.2.2 vanilla from our testing. We're currently thinking it was introduced in patch 11.1.2.2.103 – but the behaviour ALSO exists in 11.1.2.3.
Ha ha ha
Good that they raised a bug for it(when it'll be resolved is a different question)
I replicated it on vanilla 11.1.2.2
@peter
Can you please send me link to this bug in oracle site. We recently upgraded to 11.1.2.2. I want to do more research before conforming it as a bug to my client.
@Kevin : Is there any work arounds??
@sundeep the only workaround(s) is to use alias or member name with alias
We have migrated our applications from 9.3.1 to 11.1.2.2 and we tried using the 11.1.2.2 Smart View with 9.3.1 Essbase and we never had this kind of an issue.
We tried on 11.1.2.2 Essbase and we don't see any of such issue.
@amarnath
Can you please send me the screen shots? That's interesting
G'day Guys,
Interestingly, I can confirm we have some clients on 11.1.2.2 (vanilla) that do NOT have the behaviour. I thought it was an essbase patch – but I'm now not sure.
I've been told that a bug 17280541 has been created, can't find it in the bug database yet (probably hasn't been confirmed by the dev team).
@peter it is not published yet, so that could be another reason why you cannot view it
Bug is still not visible, I´m waiting for it as well…
best regards,
André
G'day Guys,
had confirmation this morning that it's intended to be fixed in Essbase Patch 11.1.2.2.104
No known date on that yet, but 103 has been out a couple of months already.
I'm trying to chase up why 17280541 isn't showing up in the Bug DB yet.
Cheers
Pete
Aloha,
Quick note for anyone still playing at home:
Hyperion Essbase Server Patch Set Update 11.1.2.3.001 fixes this problem for 11.1.2.3
Defect Number:
16731679, 16688700, 16688752, 16731662, 16688752
Defect Desc:
Alias for shared members is not displayed when alias is set to Default.
Still no word on a the patch date for 11.1.2.2 – figure they wanted to patch the latest version first.
Cheers
Pete
It got fixed in 11.1.2.3.001,just applied and tested it.
We just migrated to 11.1.2.2 and have exactly this issue
@anon try patching to 11.1.2.2.104
Hiii
Guys I have an issue with Alias in my application which the aliases appear in smart view but don't appear in web application just member name . i am using version 11.1.2.3 . Is any one face same issue before ???
I take that you mean Planning web, are you using Alias in the form properties?
How can I eliminate duplicate result in SmartView?
what do you mean by duplicate results? member repeated? double numbers