TM1 Forum

Hi,

This is super crazy, and I was wondering if you guys have seen this issue.
I have a websheet with 2 row dimensions ( TM1RPTRow formulas both using an MDX statement ). The First Dimension, is a hierarchy with 2 levels, so by default, the websheet opens with only Level 1 elements. So the user clicks the plus sign to expand the Leafs and this is where they enter the data. So she collapse that element without recalculating data ( data is still in green ). After collapsing, the green cells remain in the same position , so for example if after expanding, the user was adjusting Row 10 of active form, after collapsing, you expect that the green cells move up, but they stay in the same row, and if the user clicks Recalculate after that, TM1 saves the data in that Row 10, which is a totally different intersection.

We are using 10.2.2 and we have the latest hot fixes. Have you ever seen this issue???

Thanks

You need to provide some screenshots. Otherwise I don't know that I can believe you.

If the rows are collapsed then the row elements would then be consolidated with no leaves. This would in theory disallow data entry if the rows were misaligned.

Thanks Lotsaram,

Here are the Screenshots

This is a very simple websheet that I created just to illustrate the issue
The sheet opens with all accounts collapsed Then One of accounts is expanded so the user can adjust the value for a Leaf cell The user adjust the value for one of the Cells, from 20 to 2000, the cell shows in green since the websheet is not calculated yet I cant attach more than 3 screenshots so will post another reply

So after the Leaf Cell value is adjusted, the Parent account is collapsed again ( without recalculating / refreshing the websheet ). As you can see, the value 2000 ( green cell ), remains in the same position, which corresponds now to a different Level 1 account
After clicking on Recalc button, the value of 2000 gets saved to the Level 1 account ( because that cell is a consolidated cell, it actually spreads it down to all leafs ) So when I expand again, I see that the cell that was adjusted ( from 20 to 2000 ), does not have the adjusted value, but the adjustment is saved under the Level 1 account!!!!! Isn't this stupid??

That would be a definite bug, log it wiyh IBM and they should recognise it as a priority to resolve. Obviously a lot has changed with web interfaces in 10.2 and things get missed.

TM1 10.2, 10.2.2 and all hot fixes we applied, have been a disaster for us. We have experienced all kinds of bugs and we had to implement so many workarounds just because of TM1 bugs, but with this one, we are screwed up!!! We go live in 3 weeks and with problems like this I don't know what we are going to do

Yes we reported to IBM as a severity 1, and first they said they cannot reproduce, it's so easy to reproduce, so we insisted they share their screen with us so we can see what they're doing, and this way they were able to reproduce.

They told us it takes 6-8 weeks for them to fix this issue

That is a very serious issue. Sometimes you do wonder what testing is done. Can you post the PMR/APAR number?

I don't know what's happening with TM1 development team, but any upgrade we have done in the past year, has had issues, once a few months ago, we upgraded from 10.2.0 to 10.2.2, and everything stopped working. If you used an alias in the SUBNM / TM1RPTROW formulas, instead of returning the Alias, it was returning the Alias repeated twice ( so for example if for location abc, the alias is "Toronto", it was returning "Toronto Toronto" ), and the if that cell is referenced in a DBRW formula, it was returning KEYERR. Then we had issues with security, then with freeze pane, then with buttons being misplaced. Scrolling in TM1Web Websheets is awful and this has not been fixed. Undo button in TM1Websheet does not work. Export to excel, even when u export as snapshot, it exports all the buttons and then if you try to saveas the excel file, it crashes excel. We have so many other issues which I don't remember now, but nothing compares with what we are experiencing right now

I'm pretty sure I ran into this issue last year on TM1 10.2 FP2 but it was "fixed" in the following interim fix pack.

My memory may not be perfect, but I can confirm this isn't a problem in TM1 10.2.2 FP2 (TM1 10.2.2.2). IBM "fixed" it by simply undoing the data change (green font) when you collapse and expand.

Hi,
Unless they have no idea what they are talking about, they told us this is a defect and it will take 6-8 weeks to get it fixed. I can confirm we are using
TM1 Build Number: 10.2.20200.55, which is their latest fix for 10.2.2
They also can reproduce

Thanks

ardi wrote:I have a websheet with 2 row dimensions ( TM1RPTRow formulas both using an MDX statement ).

In your Active Form, are it's two row dimensions in immediately consecutive columns ?
Or did you insert a column between the two columns holding the two row dimensions ?

The latter is not supported according to the TM1 9.5.2 User Guide, quote:
"You cannot, however, insert a column between two row dimensions on an Active Form because that would disrupt the rows."

ardi wrote: Scrolling in TM1Web Websheets is awful and this has not been fixed.

What value have you set for the new TM1 Web configuration parameter WebsheetBackgroundRecalculationMode introduced with TM1 Web 10.2.2 FP1 ?
What happens when you set it to 2 ?


Regarding the new TM1 Web configuration parameter WebsheetBackgroundRecalculationMode see the IBM Technote 7043558 =>

http://www-01.ibm.com/support/docview.w ... wg27043558
TM1 10.2.2 FP1 - WebsheetBackgroundRecalculationMode parameter added to the tm1web_config.xml file


You may start a new thread for your scrolling issue.