Greetings fellow TM1 developers!
I havent had any problems in the past with äö letters in dimension names when making calculations. Now we upgraded customers environment from 10.1 to 10.2 and every now and then TM1 decides to f* up all calculations that involve "äö" letters in them randomly. When I update the calculation it works fine but after a while it changes then back to "squares". This issue must be related to text coding (standard) somehow but is there any settings I can change so it would recognize ä and ö letters without a problem? Couldnt find answer in the internet after few hours of googling so Im getting desperate.
Thanks to all those who answer in advance!
Problem with umlauts in calculations
-
- MVP
- Posts: 170
- Joined: Fri Dec 10, 2010 4:07 pm
- OLAP Product: TM1
- Version: [2.x ...] 11.x / PAL 2.0.9
- Excel Version: Excel 2013-2016
- Location: Germany
Re: Problem with umlauts in calculations
TM1 10.2 FP1 has solved my issues with signs like "&" in dim names, which came along with 10.2.
I had no issues with prior TM1 versions and same dim names. Not sure if you have already applied the FP, but it's worth to try it, before you open a new SR.
I had no issues with prior TM1 versions and same dim names. Not sure if you have already applied the FP, but it's worth to try it, before you open a new SR.
-
- Posts: 16
- Joined: Wed Aug 17, 2011 10:40 am
- OLAP Product: Planning, TM1
- Version: 9.5.1
- Excel Version: 2007
Re: Problem with umlauts in calculations
Thanks for the answer. Ill try if FP1 would solve this problem.
Re: Problem with umlauts in calculations
TM1 10.2.0 FP1 and TM1 10.2.0 FP2 are case sensitive with Umlauts like ä, ü, ö or á, ò in object names.
Just try entering element names in the Dimension Editor.
With "normal" letters you will not succeed.
When using DBRW() and entering the element names with the wrong case of the Umlaut, you will get a "key error", but typing all the other "normal" letters upper or lower case as you like it will be fine.
I haven't checked if UnicodeUpperLowerCase would have an effect on this behaviour.
Just try entering element names in the Dimension Editor.
With "normal" letters you will not succeed.
When using DBRW() and entering the element names with the wrong case of the Umlaut, you will get a "key error", but typing all the other "normal" letters upper or lower case as you like it will be fine.
I haven't checked if UnicodeUpperLowerCase would have an effect on this behaviour.
- Attachments
-
- case_sensitivity.JPG (47.68 KiB) Viewed 3258 times
-
- Umlauts in TM1 10.2 FP1 are case sensitive in object names.
- case_sensitivity_2.JPG (28.1 KiB) Viewed 3258 times