What is this about? Well I guess you’ll have to read till the end 🙂
Conversion is a big deal. Oh no not the religious conversion 🙂 I’m talking about converting Excel Add-in users to Smart View. (It was hard for me to use Smart View in the beginning)
So there was this question where he was wondering whether I knew about an option in Smart View to drill down on a shared member (parent member which is shared in an alternate hierarchy)
I was like “No you cannot do that in Add-in, it stops the drill down if the alternate hierarchy parent is there”. I didn’t say that aloud.
I’m like I don’t know how to do that in Add-in and you are asking me “How can I still down on a shared member in Smart View?”
In grid clients (for example, Oracle Hyperion Smart View for Office), you can reference shared members as unique from their base members by typing them with a qualified name (for example, [Parent].[Child]). Shared members can be referenced with qualified names even if you have not set the outline to enable duplicate member names.
Drilling down on 150 returns nothing if interpreted as the shared member; or, return 100 10 and 100-20 if interpreted as the regular member.
Drilling up on 150 returns Test1 if interpreted as the shared member; or, return 100 if interpreted as the regular member.
If Test1 is on the worksheet and very close to 150, Essbase Server understands that 150 is the shared member and drilling down does not result in the children, 100-10 and 100-20.
If Test1 is not on the worksheet or members are in between them, Essbase Server understands 150 to be the regular member so drilling down results in the children 100-10 and 100-20.
I was first thinking that it could be a Smart View/Excel Add-in version issue (Kishore had an older and I’m using the latest).
I looked at my Software inventory 😉 and was able to get an older version of Add-in and Smart View.
I patched it to 220.127.116.11.001, just because this patch fixed the issue with the way Shared members were showing up in Smart View (shared shows up as unique member) and see whether this behavior started from that patch and no one noticed it. You can read more about the issue here.
It is confirmed that from 18.104.22.168.001 onwards you can now drill down on a shared member.