Problem after upgrading from TM1 10.2.2 to 10.3

Post Reply
jack_008
Posts: 12
Joined: Wed Sep 28, 2016 2:20 pm
OLAP Product: TM1
Version: 10.3
Excel Version: Excel 2013

Problem after upgrading from TM1 10.2.2 to 10.3

Post by jack_008 » Wed Nov 01, 2017 1:46 pm

We have recently upgraded from TM1 10.2.2 to TM1 10.3

We are transferring data from one cube to other.The problem we are facing is the cell values in a target cube are unclear for e.g.

330 displays as 3300(Here 330 is the value in source cube & the value in the target cube appears to be 3300)

Similar situation for other records below.

600000 as 59999999999999000
20000 as 20000000000000000
71461 as 71461000000000000
80000 as 79999999999999000

Can anyone help me out with this issue.

Thanks in advance !

User avatar
Steve Rowe
Site Admin
Posts: 1678
Joined: Wed May 14, 2008 4:25 pm
OLAP Product: TM1
Version: 10.2.2., PAW
Excel Version: Nearly all of them

Re: Problem after upgrading from TM1 10.2.2 to 10.3

Post by Steve Rowe » Wed Nov 01, 2017 2:12 pm

Obviously sounds odd, have you checked if you have a formatting issue? Which client environment are you seeing the issue and what formatting is in place?

If you look in the transaction log what value is being written to the cube?

lotsaram
MVP
Posts: 3006
Joined: Fri Mar 13, 2009 11:14 am
OLAP Product: TM1, CX
Version: TM1 10.2.2 PA 2.0x
Excel Version: 2010 2013 365
Location: Switzerland

Re: Problem after upgrading from TM1 10.2.2 to 10.3

Post by lotsaram » Wed Nov 01, 2017 3:21 pm

jack_008 wrote:
Wed Nov 01, 2017 1:46 pm
We have recently upgraded from TM1 10.2.2 to TM1 10.3
What exactly do you mean by TM1 10.3? As far as I am aware no such version exists. "10.3" was used to refer to the server version of the 1st iteration of Planning Analytics cloud and AFAIK exist only in the cloud version and is not available on premise (and never will be). Planning Analytics Local is TM1 v11.
Please place all requests for help in a public thread. I will not answer PMs requesting assistance.

pandinus
Posts: 77
Joined: Tue Mar 18, 2014 8:02 am
OLAP Product: TM1, Cognos Express
Version: 10.2.2
Excel Version: 2013

Re: Problem after upgrading from TM1 10.2.2 to 10.3

Post by pandinus » Tue Nov 07, 2017 11:18 am

Since TM1 10.2.2 FP6 (and also in Planning Analytics 2.x) there is an issue (IBM calls this a feature) with the StringToNumber functionality in some cases where a specific decimal-separator is defined on the server OS level.

This may be the cause for what you are seeing right now.

The solution that IBM provides technically isn't a solution, but rather a workaround. By using NValue instead of StringToNumber the correct data will be transferred to the target cube.

Post Reply