TM1 Web - Number Pad vs Top Row Numbers Percentages

Post Reply
declanr
MVP
Posts: 1831
Joined: Mon Dec 05, 2011 11:51 am
OLAP Product: Cognos TM1
Version: PA2.0 and most of the old ones
Excel Version: All of em
Location: Manchester, United Kingdom
Contact:

TM1 Web - Number Pad vs Top Row Numbers Percentages

Post by declanr »

All,

This may be a well known issue already but I can't seem to find anything on it (possibility just not really knowing what to search for):

Have a websheet with a percentage formatted cell to input to:
# Input 0.5 using the number pad of the keyboard results in 50%
# Input 0.5 using the top row numbers of the keyboard results in 0.5%

I've always just used a laptop so I've never actually noticed this myself but do seem to remember in the back of my head that someone mentioned it a while ago and as such think it may have been this way for a few version.

Using TM1 10.1.1 and IE9.

Is this a known TM1 issue or just a common system thing that occurs in everything and not just TM1??

P.S I've always used a laptop so have never really had the privilege of a number pad with TM1 before!
Declan Rodger
Steven Marshall
Posts: 7
Joined: Wed Feb 04, 2009 10:03 pm
OLAP Product: TM1
Version: TM1 10.1.1
Excel Version: 2003-2010

Re: TM1 Web - Number Pad vs Top Row Numbers Percentages

Post by Steven Marshall »

Hi Declan,

I came across this a couple of months back with some end-user testing. Very confusing from a user perspective and not one I've come across in versions prior to 10.1 but again I've only really used a laptop.

If memory serves negative values appeared to work ok with either pad.

It's logged under PM83792 with a fix expected in 10.2

Cheers,
Steven
declanr
MVP
Posts: 1831
Joined: Mon Dec 05, 2011 11:51 am
OLAP Product: Cognos TM1
Version: PA2.0 and most of the old ones
Excel Version: All of em
Location: Manchester, United Kingdom
Contact:

Re: TM1 Web - Number Pad vs Top Row Numbers Percentages

Post by declanr »

Steven,

Spot on about the negative numbers etc & checked 10.2, it resolved the issue.

Now I won't be upgrading the production environment in question to 10.2 for a while so fingers crossed a fix pack for 10.1 resolves this in the near future.

Thanks,
Declan
Declan Rodger
Post Reply