Are Varying Attributes as Disappointing in Practice as I'm Seeing?
February 10 2012 at 12:42 PM No score for this post
from IP address 184.108.40.206
I have a ready made use case for varying attributes, and I've tested them out with exciting results. Smart View has a way of accessing them via different perspectives, and the classic add-in does the most useful perspective mode, the "reality" one. This has real potential to allow for a nice dimensional design in the cube I'm buillding.
BUT... There is no method to automate their maintenance, except maybe Essbase Studio has some amount of capability, which I'm not sure can be data-driven or not (and which wouldn't help me anyway since we don't use it).
The mose outrageous thing I'm seeing here is that evidently normal methods to assign a attributes (load rule, API, EAS), which I would presumably be able to employ for a member whose attribute has never changed, and would thus apply across the board to all perspectives, don't work. The attribute appears to be assigned in the outline editor, but data queries do not act as if there is any assignment at all. Only after adding the attribute, with a range, through EAS do I get any results in the queries.
I have a few hundred members in the normal dimension and several dozen in the attribute dimension. Exactly 10 base members have had their attribute change over time. But in order to have varying attributes in this database, I'd have to manually re-add and manage the attributes for all of my few hundred base members and not just the 10.
It's bad enough I can't use a load rule or the Java API (as many of you know I would very much like to use) to assign the attributes that acually vary, but it's just unacceptable that now I can't use them to assign the attributes to ANY of the base members.
Because the benefits seem so nice, I was just about to decide to bite the bullet and commit to manually managing any of the members that should wind up needing their attributes to vary over time. I have a query into the SQL repository to identify them. But I'm not going to be in charge of manually assigning attributes to every new member that comes along because the automated methods I have to do that now would no longer work.
Why, oh why, would they cripple such a very nice feature by making it so hard to set up and maintain? Someone please tell me I'm missing something!
Scoring disabled. You must be logged in to score posts.