TM1 Forum

Hello All,

I've been looking around at this subject, online and in the documentation, and need to ask for a little assistance.

I am running TM1 9.5.1 and Cognos BI 10

I have a cube of 7 dimension of which one dimension represents a GL Account. This dimension contains two alias' which can be applied by the user, one called "Code and Name", which simply shows the element with a name, eg "1000 - Goodwill" and the other called "Longname", which simply shows "Goodwill" against the element "1000".

When the cube is published via Framework Manager, I check the language box and when I open the cube in Report Studio, the members displayed to me are the "Code and Name". There are no options for me to select the code itself, ie "1000", nor the alias "Longname", ie "Goodwill".....all this is limiting the usefulness of the reporting in BI to various different user groups.

Looking at things I have read there does appear to be an check I need to make when publishing the cube in Framework Manager which is to tick the "Alias" button, but there is also a reference to me needing to define some levels in the control cube {HierarchyProperties.

Looking at this cube and reading the documentation, I am a bit confused with what I actually need to do in this cube. Can someone help me, with reference to my example above.

Many thanks
Ajay

OK, finally worked out what the {HierarchyProperties does, but leaves me with the final issue....which is at the point of publishing the TM1 cube in Framework Manager, you seem to be able to only select one alias per dimension in the cube to be published.

If you have more than one alias, there appears to be no other way of bringing these alias' into Report Studio.

If anyone knows how this can be done, please let me know.

Thanks
Ajay

Ajay wrote:....which is at the point of publishing the TM1 cube in Framework Manager, you seem to be able to only select one alias per dimension in the cube to be published.

If you have more than one alias, there appears to be no other way of bringing these alias' into Report Studio.

Hi Ajay:

I don't think you can bring them over in the way you're hoping to - I think you're limited to one TM1 Alias selection per language per dimension per Framework Manager package. In other words, there's no option in Report Studio (or other studios) that I'm aware of that lets you toggle between aliases like you're used to in the TM1 subset editor.

I believe you can access/use TM1 attributes in Report Studio, but I'm a bit rusty/fuzzy on where you go to do that. Accessing TM1 attributes in this way may help get you the descriptive information you need for a report, even if it isn't as simple or flexible as toggling different aliases.

Regards,
Mike

Thanks for getting back to me Mike.

I was beginning to feel like I was the only one with a post that no-one wanted to answer !!!

This certainly feels like a bit of a let down in the integration between TM1 and Report Studio, you would expect that more than one alias should come through.

I am going to try another approach, which is to publish the }ElementAttributes_Account cube as this will at least have all N elements and their alias values, and then pull these across onto the report as an additional column....hopefully this will work.

Would you foresee any issues doing this ?

Kind regards
Ajay

I haven't worked with Cog 10 beyond basic product training but if memory serves me correctly from 8.4 (it may not, and things may have changed ...) you can't publish TM1 control objects as FM packages so you would have to create a replica 2D lookup cube as a copy of the attribute cube and publish that instead.

I think you can use attributes in the Studios though (certainly you can in report studio, not so sure about analysis studio) so your best bet might be to create a copy of the alias as a string attribute which you could then pull through as an additional column in a report.

Yes, I was thinking of creating a second cube but not from the angle of not being able to publish control cubes, but more from having a normal named cube which users can identify with, but your point is valid.

I think a TI driven copy of the cube every night will do the trick. Just testing now whether I need to add an additional dimension just in case I get an error complaining of no measures dimension existing !!!

Hi All

Thought I would post an update on where I am with this.

The second cube was created in TM1 and then published in Framework Manager.

However, an error message is thrown out when trying to put the two cubes into the same report studio report. Looks like you can only have one TM1 cube for each report.

Ajay

You should be able to use the attributes of elements in Report Studio. If you expand either the hierarchy (if you have a non level based hierarchy) or the levels (if you have a level based hierarchy) you will see additional items. These are the element attributes and can be used as the display text instead of the alias you picked in framework manager. Simply unlock the report and click on the text representing the element and change the data item value to an attribute of your choosing from the hierarchy.

Ajay,
you can reference multiple cubes in one report. All you need to do is right click on model namespace and run matadata wizard and import the new cube in the FM project. Then edit the definition of the package you want the new cube to be included into and select the cubes which you want to include in the package. Then publish and create reports. I have created reports using multiple cubes and it does work. I hope the steps are clear enough.

Thanks Guys, it is encouraging to see the ideas out there.

@Planning Dev - I think from what you are saying, is that, instead of using alias' in the TM1 dimension, create some text attributes instead and these will automatically be published in FM. I can then use these in my report studio report. Is this correct ?

@Laxman Kadam - At the moment I have brought in a crosstab from one cube, and created a second cube to bring through decriptive items in a list, as a workaround to the issue that I was having. Both have been added into a table. However, both have seperate queries. Will your suggestion provide a single query which access both cubes ?

Thanks Guys

@PlanningDev...thankyou.

This worked. I created text attributes in TM1 which mirrored the alias', and then when I published the cube, I unticked the alias box so that only the element would be published.

Once done, I could see the members plus the attributes I created, which I was able to simply drag across onto my report.

Phew !!! Point to note if publishing TM1 cubes into Report Studio.

Thanks
Ajay