Add Elements to own Control Dimension

Post Reply
HighKeys
Posts: 117
Joined: Fri Aug 09, 2019 10:11 am
OLAP Product: TM1 / TM1 Web / Perspectives
Version: Planning Analytics V2.0.9
Excel Version: Office 365

Add Elements to own Control Dimension

Post by HighKeys »

Hello friends,

i'm stucking at adding an element to my own created Control Dimension.

I used a TI procress to create a control Dimension called "}Global Assumptions" now i want to add an element called "TodaysDate" so i try to add it with a small TI pro where i added in the Epilog

"DimensionElementInsert( pDimName, ' ', pElementName, pElementType );"

Where
pDimName = }Global Assumptions
pElementName = TodaysDate
pElementType = S


i get no error when i run the process but the element doent get added.

Someone know where my mistake is?
I want to add this to control dimensions to hide it from "Normal" users :)


THanks for your help
HighKeys
Posts: 117
Joined: Fri Aug 09, 2019 10:11 am
OLAP Product: TM1 / TM1 Web / Perspectives
Version: Planning Analytics V2.0.9
Excel Version: Office 365

Re: Add Elements to own Control Dimension

Post by HighKeys »

Hello Again,

my fault, i can't read...

I put the code on the epilog but the docs says it can't be there...


"DimensionElementInsert adds an element to a dimension. You can use this function to add numeric, string, or consolidated elements. You can't use this function in the Data or Epilog procedures of a TurboIntegrator process."
ascheevel
Community Contributor
Posts: 287
Joined: Fri Feb 15, 2013 5:49 pm
OLAP Product: TM1
Version: PA 2.0.9.1
Excel Version: 365
Location: Minneapolis, USA

Re: Add Elements to own Control Dimension

Post by ascheevel »

Check out DimensionElementInsertDirect
User avatar
paulsimon
MVP
Posts: 808
Joined: Sat Sep 03, 2011 11:10 pm
OLAP Product: TM1
Version: PA 2.0.5
Excel Version: 2016
Contact:

Re: Add Elements to own Control Dimension

Post by paulsimon »

Hi

You have solved your own problem. Put the code in the Prolog or MetaData and it will work.

However, I would advise you against starting dimensions with }. It can become difficult to differentiate these from real Control Dimensions. You run the risk that IBM might use this dimension name at some point in the future.

Instead, start the dimension with a normal alphabetic character, possibly a prefix such as za_ to make them sort at the bottom. If you want to hide the dimension from users then just use DimensionSecurity and NONE.

Regards

Paul
Post Reply