F9 in the Cube viewer

Suggest and discuss enhancements for TM1
Post Reply
Wim Gielis
MVP
Posts: 3105
Joined: Mon Dec 29, 2008 6:26 pm
OLAP Product: TM1, Jedox
Version: PAL 2.0.9.18
Excel Version: Microsoft 365
Location: Brussels, Belgium
Contact:

F9 in the Cube viewer

Post by Wim Gielis »

Please, when pressing F9 in the Cube viewer for recalculating the view,

DO NOT go back to the first cell in the view !!!

It's very annoying to do input cell by cell, pressing F9 to recalc, and then having to go back to the selected cell.

Thanks IBM.
Best regards,

Wim Gielis

IBM Champion 2024
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
User avatar
jim wood
Site Admin
Posts: 3951
Joined: Wed May 14, 2008 1:51 pm
OLAP Product: TM1
Version: PA 2.0.7
Excel Version: Office 365
Location: 37 East 18th Street New York
Contact:

Re: F9 in the Cube viewer

Post by jim wood »

It's very annoying. I'm sure there will be some bizarre reason for it. There always is.
Struggling through the quagmire of life to reach the other side of who knows where.
Shop at Amazon
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
User avatar
Alan Kirk
Site Admin
Posts: 6606
Joined: Sun May 11, 2008 2:30 am
OLAP Product: TM1
Version: PA2.0.9.18 Classic NO PAW!
Excel Version: 2013 and Office 365
Location: Sydney, Australia
Contact:

Re: F9 in the Cube viewer

Post by Alan Kirk »

jim wood wrote:It's very annoying. I'm sure there will be some bizarre reason for it. There always is.
Though I'm hardly a staunch supporter of IBM... I'm not sure that they really have a lot of choice in this case. The problem is that the rows and columns may have changed since the last recalculation was done, and Cube Viewer has no way of knowing whether they have or not.

For example, you hit [F9], see the numbers, a scheduled upload occurs, then you hit [F9] again and... whatever was at (say) row 17 column 12 where your cursor was, may no longer be at that position. In fact the value you had your cursor on may no longer even exist if it has been zeroed out. Certainly you could reposition the cursor to the same relative position in the grid easily enough but I'm not sure that that will help if it means that you land on an entirely different number, and also you could only do it if the recalculated view had at least as many rows and columns as the original view did.

The only way that you could implement this is to, after calculation, check that the rows and columns of the recalculated view corresponded to the rows and columns of the view before it was calculated. If they did, only then could you relocate the cursor on the same coordinates as they were before. (Alternatively if you want to position it on the same element combination, you'd need to check whether that combination was in fact returned as part of the recalculated view.)

All of those options would take overhead processing, and the designers probably opted for speed and just went with the simplest option of returning the cursor to row 1, column 1.
"To them, equipment failure is terrifying. To me, it’s 'Tuesday.' "
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
Wim Gielis
MVP
Posts: 3105
Joined: Mon Dec 29, 2008 6:26 pm
OLAP Product: TM1, Jedox
Version: PAL 2.0.9.18
Excel Version: Microsoft 365
Location: Brussels, Belgium
Contact:

Re: F9 in the Cube viewer

Post by Wim Gielis »

Good point Alan, I hadn't thought of that possibility.
Best regards,

Wim Gielis

IBM Champion 2024
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
Post Reply