TM1 Forum

I am facing problem while including a new Text/Numeric Attribute the elements available in a dimension called period.

Period has all months ranging from 2010 to 2020 and the months are in the following structure 201001, 201002, 201003 etc. There are many text attributes available for all these elements. I want to add another text attribute called 'BudgetVoyage' and want to allot year to the corresponding month, let say for 201204 - the attrib value will be 2012 and I want to utilise this value in rules using ATTRS() to fetch the budget year of the selected period. But when I trying to create a new attribute, I am able to create but unable to set new values to the new attribute.

I am furnishing an example:

['Budget','ContainerCount','BudgetedVoyage','TEUSplit_Calc']=
['Budget','ContainerCount','2012','BudgetedVoyage','TEU']\['Budget','AllContainerSizes','NonSlots','ContainerCount','2012','BudgetedVoyage','TEU'];

Instead of using these hard coded values, I want system to consider corresponding dynamic budget year of any selected period

I see "Cannot Set Attribute Values" message. What would be the reason for this, can any one help me out of this issue? Or is there any other alternative to achieve this?

Points to Ponder:
-Period Dimension is utilized by many other cubes.
-Even its Attributes are utilized by other cubes.
-the new attribute values or attribute name is not existing in the current attribute values or attribute names respectively.
- User may select either month(which is leaf level) or year(which is consolidation level) for budget purpose, system have to pick the budget year.

Period
2011(C)

• -201101(N)
  -201102(N)
  -201103(N)
  -201104(N)
  -201105(N)
  -201106(N)
  -201107(N)
  -201108(N)
  -201109(N)
  -201110(N)
  -201111(N)
  -201112(N)

What are you trying to name this new attribute? You can't use the name YEAR because that is a reserved word as it is also a rules language function. Try a slightly different variation on the name and it should work.

Sounds to me like it is either the attribute editor having a moment, or you have defined your attribute as an Alias rather than a Text attribute. If the attribute editor truly isn't applying the entries that you have made and it is a Text attribute, try entering the data directly into the appropriate }ElementAttributes cube, or just closing and re-opening the attribute editor.