Re: If You Could ask the TM1 Development Team a Question....
Posted: Fri Jan 18, 2013 9:50 am
TM1 support for Multiple Languages
Within a dimension it is possible to give the Elements, eg a French, German, etc Alias. However, there is currently no way to change the name of the dimension itself - it will always be in English or whatever the develop name is. This is becoming more of an issue now as TM1 is used across national boundaries.
What I would like to see if something along these lines:
A Client Property allowing users to select their preferred Alias.
a) The ability to Alias all TM1 Objects, not just Elements, but the Dimension Names, Cube Names, Process Names, Chore Names, View Names, Subset Names, etc.
(This could also be handy for general development, eg many of us add a few general Analysis dimensions to cubes for future expansion, and if we use these it would be handy to be able to give Analysis 1 its new name via an Alias such as Projects).
b) The ability to have all objects in Server Explorer and other front ends automatically display using the users preferred Alias.
In practice I often have at least two aliases per language, eg Description followed by Code and Code followed by Description.
To take this one step further, rather than re-using the concept of Aliases, would it be possible to specify the language as a subdivision of an Alias? This could then be linked to the language selected in Windows.
For example could I provide a series of language selections for a Description Text Attribute, and then use a rule to combine that in a Aliases with the Code, to give the Description - Code and Code - Description Aliases?
Regards
Paul Simon
Within a dimension it is possible to give the Elements, eg a French, German, etc Alias. However, there is currently no way to change the name of the dimension itself - it will always be in English or whatever the develop name is. This is becoming more of an issue now as TM1 is used across national boundaries.
What I would like to see if something along these lines:
A Client Property allowing users to select their preferred Alias.
a) The ability to Alias all TM1 Objects, not just Elements, but the Dimension Names, Cube Names, Process Names, Chore Names, View Names, Subset Names, etc.
(This could also be handy for general development, eg many of us add a few general Analysis dimensions to cubes for future expansion, and if we use these it would be handy to be able to give Analysis 1 its new name via an Alias such as Projects).
b) The ability to have all objects in Server Explorer and other front ends automatically display using the users preferred Alias.
In practice I often have at least two aliases per language, eg Description followed by Code and Code followed by Description.
To take this one step further, rather than re-using the concept of Aliases, would it be possible to specify the language as a subdivision of an Alias? This could then be linked to the language selected in Windows.
For example could I provide a series of language selections for a Description Text Attribute, and then use a rule to combine that in a Aliases with the Code, to give the Description - Code and Code - Description Aliases?
Regards
Paul Simon