Cognos Analytics

Hi ,
We have defined Named level in Tm1 Cubes hierarchy in }HierarchyProperties cube but the issue is attributes defined for the dimension are present in each level but they are not accessible at dimension or element level. I mean , you can not use directly rolevalue('attributename',Element) function. If you use this function it gives error like ..
Attribute use is not defined in the system. 

To make it use in report , we need to drag the attribute in the query and then use it. Then the problem here is , we have different attribute defined for each alternate heirarchy for same element. Ex One Element is present in 4 different alternate heirarchy at different level then each is having its own display value.
        T Year -Month is dimension , YTD,YTD,Month are alternate heirarchies, then named levels are defined as Total, year,Half,Quarter,Month. we can see no attribute is available here, all the attributes are within each levels. as shown below. But the if you refer element of Month level and use Member description attribute from Total level then report throwing error. Normally , attributes should be linked to element not the level from which element is appearing.

Is it possible somehow , to make the attributes available at the dimension level instead of inside the level defined.

I am not sure i have explained it properly. 

Report developing is complex, need to select different alternate heirarchy from the prompt page and then based on the selected drill path and drill level , report need to show that drill path and till the selected drill level with its respective attribute.


Thanks in advance for your help.

------------------------------
sumeet yadav
------------------------------

------------------------------
sumeet yadav
------------------------------

#CognosAnalyticswithWatson

Thanks in advance if anyone have gone through this issue.

Another main issue is why i am looking for Level based hierarchy, because we have multiple level and right now i am using Root element and then applying descendant over it to go to the particular level but the issue inusing root level is , user who dont have access to root element will get error while running the report.

so i have to look for some other alternative way to acess the particular level in heirarchy. If there are any other better way kindly suggest.



------------------------------
sumeet yadav
------------------------------

Original Message:
Sent: Mon December 26, 2022 06:05 AM
From: sumeet yadav
Subject: Attributes not available outside named defined level in dimensions in tm1 cube

Hi ,
We have defined Named level in Tm1 Cubes hierarchy in }HierarchyProperties cube but the issue is attributes defined for the dimension are present in each level but they are not accessible at dimension or element level. I mean , you can not use directly rolevalue('attributename',Element) function. If you use this function it gives error like ..
Attribute use is not defined in the system. 

To make it use in report , we need to drag the attribute in the query and then use it. Then the problem here is , we have different attribute defined for each alternate heirarchy for same element. Ex One Element is present in 4 different alternate heirarchy at different level then each is having its own display value.
        T Year -Month is dimension , YTD,YTD,Month are alternate heirarchies, then named levels are defined as Total, year,Half,Quarter,Month. we can see no attribute is available here, all the attributes are within each levels. as shown below. But the if you refer element of Month level and use Member description attribute from Total level then report throwing error. Normally , attributes should be linked to element not the level from which element is appearing.

Is it possible somehow , to make the attributes available at the dimension level instead of inside the level defined.

I am not sure i have explained it properly. 

Report developing is complex, need to select different alternate heirarchy from the prompt page and then based on the selected drill path and drill level , report need to show that drill path and till the selected drill level with its respective attribute.


Thanks in advance for your help.

------------------------------
sumeet yadav
------------------------------

------------------------------
sumeet yadav
------------------------------

#CognosAnalyticswithWatson

Which version are you using? I believe a recent engine upgrade improved the usability of member properties against named levels. 

I also have a TM1 cube with named levels:


If I had a set going against a single level I could do something like this: roleValue('YYYYMM',[Timeline Set])
The MDX looks fine:
WITH
MEMBER [R_SCENARIO].[R_SCENARIO].[XQE_NULL_CM3] AS 'NULL', SOLVE_ORDER = 65535
SELECT
{ [R_TIMELINE].[R_TIMELINE].[FY Jun 2021 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Jul 2021 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Aug 2021 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Sep 2021 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Oct 2021 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Nov 2021 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Dec 2021 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Jan 2021 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Feb 2021 YTD]
}

DIMENSION PROPERTIES PARENT_LEVEL, PARENT_UNIQUE_NAME, [R_TIMELINE].[YYYYMM] ON AXIS(0)

, {[R_SCENARIO].[R_SCENARIO].[XQE_NULL_CM3]}

DIMENSION PROPERTIES PARENT_LEVEL, PARENT_UNIQUE_NAME ON AXIS(1)

FROM [REPORTING] CELL PROPERTIES CELL_ORDINAL, FORMAT_STRING, VALUE

The problem is if the set is a multilevel set using roleValue returns an error:
Frustratingly this works perfectly in cubes without named levels. 

Now this is where we start having differences. When I pull in a member property directly into the crosstab, it works great:



The MDX looks good too:
WITH
MEMBER [R_SCENARIO].[R_SCENARIO].[XQE_V5M_CM1] AS '([R_SCENARIO].[R_SCENARIO].DEFAULTMEMBER)'
, SOLVE_ORDER = 4
, MEMBER_CAPTION = 'Timeline Set'
SELECT

CROSSJOIN(
{
[R_TIMELINE].[R_TIMELINE].[Fiscal Year Apr to Mar 2022]
, [R_TIMELINE].[R_TIMELINE].[FY Dec 2022 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Dec 2022 YTD^FY Aug 2022]
, [R_TIMELINE].[R_TIMELINE].[FY Dec 2022 YTD^FY Oct 2022]}

, {[R_SCENARIO].[R_SCENARIO].[XQE_V5M_CM1]})

DIMENSION PROPERTIES PARENT_LEVEL, PARENT_UNIQUE_NAME, [R_TIMELINE].[YYYYMM] ON AXIS(0)

FROM [REPORTING] CELL PROPERTIES CELL_ORDINAL, FORMAT_STRING, VALUE

The YYYYMM is appearing as a property on the axis, exactly like it should be. I do remember that pulling the member property from a different level caused issues, but it seems to be working great now. 

I'm testing this on 11.2.1

------------------------------
Paul Mendelson
------------------------------

Original Message:
Sent: Mon December 26, 2022 06:05 AM
From: sumeet yadav
Subject: Attributes not available outside named defined level in dimensions in tm1 cube

Hi ,
We have defined Named level in Tm1 Cubes hierarchy in }HierarchyProperties cube but the issue is attributes defined for the dimension are present in each level but they are not accessible at dimension or element level. I mean , you can not use directly rolevalue('attributename',Element) function. If you use this function it gives error like ..
Attribute use is not defined in the system. 

To make it use in report , we need to drag the attribute in the query and then use it. Then the problem here is , we have different attribute defined for each alternate heirarchy for same element. Ex One Element is present in 4 different alternate heirarchy at different level then each is having its own display value.
        T Year -Month is dimension , YTD,YTD,Month are alternate heirarchies, then named levels are defined as Total, year,Half,Quarter,Month. we can see no attribute is available here, all the attributes are within each levels. as shown below. But the if you refer element of Month level and use Member description attribute from Total level then report throwing error. Normally , attributes should be linked to element not the level from which element is appearing.

Is it possible somehow , to make the attributes available at the dimension level instead of inside the level defined.

I am not sure i have explained it properly. 

Report developing is complex, need to select different alternate heirarchy from the prompt page and then based on the selected drill path and drill level , report need to show that drill path and till the selected drill level with its respective attribute.


Thanks in advance for your help.

------------------------------
sumeet yadav
------------------------------

------------------------------
sumeet yadav
------------------------------

#CognosAnalyticswithWatson

Thanks for the reply, 
Yes you are right, in this version below, I can use the attribute directly from the Dimension instead of using in RoleValue. As in my case , Alternate hierarchies are dynamic based on the user selection, so attribute will also be dynamic, so i have used below to use as attribute , and it is working fine. 

#prompt('P_DrillPath','token')#.#sb(
substitute('''','',
substitute('''','',
prompt('P_Attribute','string')
)
)
)#

P_DrillPath - is the Hierarchy name , P_Attribute is the attribute corresponding to this hierarchy, passing from different cube , where we stored the information of all the alternate hierarchies and their attributes and no. of levels each hierarchies having.


Version :- 



------------------------------
sumeet yadav
------------------------------

Original Message:
Sent: Wed December 28, 2022 07:26 AM
From: Paul Mendelson
Subject: Attributes not available outside named defined level in dimensions in tm1 cube

Which version are you using? I believe a recent engine upgrade improved the usability of member properties against named levels. 

I also have a TM1 cube with named levels:


If I had a set going against a single level I could do something like this: roleValue('YYYYMM',[Timeline Set])
The MDX looks fine:
WITH
MEMBER [R_SCENARIO].[R_SCENARIO].[XQE_NULL_CM3] AS 'NULL', SOLVE_ORDER = 65535
SELECT
{ [R_TIMELINE].[R_TIMELINE].[FY Jun 2021 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Jul 2021 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Aug 2021 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Sep 2021 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Oct 2021 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Nov 2021 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Dec 2021 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Jan 2021 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Feb 2021 YTD]
}

DIMENSION PROPERTIES PARENT_LEVEL, PARENT_UNIQUE_NAME, [R_TIMELINE].[YYYYMM] ON AXIS(0)

, {[R_SCENARIO].[R_SCENARIO].[XQE_NULL_CM3]}

DIMENSION PROPERTIES PARENT_LEVEL, PARENT_UNIQUE_NAME ON AXIS(1)

FROM [REPORTING] CELL PROPERTIES CELL_ORDINAL, FORMAT_STRING, VALUE

The problem is if the set is a multilevel set using roleValue returns an error:
Frustratingly this works perfectly in cubes without named levels. 

Now this is where we start having differences. When I pull in a member property directly into the crosstab, it works great:



The MDX looks good too:
WITH
MEMBER [R_SCENARIO].[R_SCENARIO].[XQE_V5M_CM1] AS '([R_SCENARIO].[R_SCENARIO].DEFAULTMEMBER)'
, SOLVE_ORDER = 4
, MEMBER_CAPTION = 'Timeline Set'
SELECT

CROSSJOIN(
{
[R_TIMELINE].[R_TIMELINE].[Fiscal Year Apr to Mar 2022]
, [R_TIMELINE].[R_TIMELINE].[FY Dec 2022 YTD]
, [R_TIMELINE].[R_TIMELINE].[FY Dec 2022 YTD^FY Aug 2022]
, [R_TIMELINE].[R_TIMELINE].[FY Dec 2022 YTD^FY Oct 2022]}

, {[R_SCENARIO].[R_SCENARIO].[XQE_V5M_CM1]})

DIMENSION PROPERTIES PARENT_LEVEL, PARENT_UNIQUE_NAME, [R_TIMELINE].[YYYYMM] ON AXIS(0)

FROM [REPORTING] CELL PROPERTIES CELL_ORDINAL, FORMAT_STRING, VALUE

The YYYYMM is appearing as a property on the axis, exactly like it should be. I do remember that pulling the member property from a different level caused issues, but it seems to be working great now. 

I'm testing this on 11.2.1

------------------------------
Paul Mendelson

Original Message:
Sent: Mon December 26, 2022 06:05 AM
From: sumeet yadav
Subject: Attributes not available outside named defined level in dimensions in tm1 cube

Hi ,
We have defined Named level in Tm1 Cubes hierarchy in }HierarchyProperties cube but the issue is attributes defined for the dimension are present in each level but they are not accessible at dimension or element level. I mean , you can not use directly rolevalue('attributename',Element) function. If you use this function it gives error like ..
Attribute use is not defined in the system. 

To make it use in report , we need to drag the attribute in the query and then use it. Then the problem here is , we have different attribute defined for each alternate heirarchy for same element. Ex One Element is present in 4 different alternate heirarchy at different level then each is having its own display value.
        T Year -Month is dimension , YTD,YTD,Month are alternate heirarchies, then named levels are defined as Total, year,Half,Quarter,Month. we can see no attribute is available here, all the attributes are within each levels. as shown below. But the if you refer element of Month level and use Member description attribute from Total level then report throwing error. Normally , attributes should be linked to element not the level from which element is appearing.

Is it possible somehow , to make the attributes available at the dimension level instead of inside the level defined.

I am not sure i have explained it properly. 

Report developing is complex, need to select different alternate heirarchy from the prompt page and then based on the selected drill path and drill level , report need to show that drill path and till the selected drill level with its respective attribute.


Thanks in advance for your help.

------------------------------
sumeet yadav
------------------------------

------------------------------
sumeet yadav
------------------------------

#CognosAnalyticswithWatson