Multi-language applications

[kastellu]

HEllo,

Is it possible to create multi-language application on dimension - element level by using different aliases. Based on user preferences or based on where in approval hierarchy you are loged in.

I know that dynamic subset can not be set to use different aliases based on attribut or any other filter type.

Example:

Product would be then listed in two different languages , based on user the alias would be different.

Thanks for help,

K

[jim wood]

Have a look at: http://www.tm1forum.com/viewtopic.php?f=3&t=5068

[kastellu]

I did, but making a replication or two instances is not what I would like to do.

If there is a possibility to call a link for application with parameters where you would set default aliases for some dimensions or at least one would be the best way.

Any other ideas , since i know that there is no way i could create dynamic subset,... is there a way to create a dynamic view based on attribute?

[Martin Ryan]

Not possible that I'm aware of. Best you could do is get the users to create their own Default subsets that use the correct alias. Or create those subsets for them and copy them into the back end folder for each of the users who require that language.

However even this will get bypassed by any publicly saved views, as they will use the publicly available subsets.

It's an interesting point though, and would be worth mentioning in the enhancements forum.

Martin

[kastellu]

What do you mean by copying it to back end folder?

Thanks

[Martin Ryan]

All of the TM1 objects are held in a directory (typically called "Data") on your server. In that directory there will be a folder for each user, e.g. jbloggs, within that folder will be folders with names like scenario}subs. This contains .sub files that represent subsets. Using the scenario dimension as an example you will have

Data\scenario}subs\Default.sub which is the public default subset for the scenario dimension
Data\jbloggs\scenario}subs\Default.sub which is the private default subset for Joe Bloggs for the scenario dimension.

You can copy these files from one place to another, e.g. from jbloggs\scenario}subs to fflintoff\scenario}subs, and then the user fflintoff will have their own duplicate copy of the subset. This is what I'm referring to when I say you can copy from one user to another.

It requires a server restart or a user login for the system to recognise that new objects have been created in this way.

Martin

[kastellu]

This is a good idea and it works but it still needs lots of manual work. Hopefully a new version of TM1 will have some new features related to localization of element data.

K

[stormrider]

If you are using websheets with active forms for your application then you can do the following:

- Have different aliases on your dimension English, Spanish, Japanese.
- Have a cube dimension by }Clients that stores the user language preference
- Return the language preference to the websheet via a DBR to the above cube utilising the tm1user function to return the logged in user
- Use the result in the tm1rptrow formula to get the correct alias for the user
- Use subnms on the columns with alias
- Use subnms for other user selections

This works even with unicode characters