9.5.2 FP2 --> 3 Issue

[AmbPin]

Hello,
I have just installed FP 3 which has caused a problem with some of our Excel authored reports in TM1 Web.
In the sample sheet shown below, the mucky orange cell is an Excel validated range using the list of months to the right. The formula shown below the mucky cell is used to initialize the selection to the current month.

Capture.PNG (5.7 KiB) Viewed 6137 times

This approach has worked fine for a ling time over several TM1 versions and fix packs, however now, in TM1 Web it no longer works the way that it has done. To be able to change the selection on the web we have to:-

• Disable automatic calculation;
• Modify the list selection;
• Press the TM1 Web recalculate button

After this we can turn automatic calculation back on and it works fine. Has anyone got any ideas why this might be happening or how we can fix/work around it.

[declanr]

Not sure as to why it did work and now it doesn't as I tend to avoid using excel formulas for such tasks anyway.

A way around it would be to just have a 2-d cube with a static picklist of Jan through to Dec and reference that in your websheet. You could obviously use a TI to populate it with the "current" month as a starting point.

Depending how you navigate to the Web report in the first instance, it is possible to have a "menu page" for each user that gives them the list of reports they can jump to through hyperlinks or action buttons, for this one they could navigate to it through an action button that before hand kicks off the TI to update your 2d-cube with "current" month.

[AmbPin]

Thanks for the ideas.

[rmackenzie]

This approach has worked fine for a ling time over several TM1 versions and fix packs, however now, in TM1 Web it no longer works the way that it has done. To be able to change the selection on the web we have to:-

That sounds annoying. Maybe some fix was made to some other issue and the treatment of evaluation of NOW was changed in the fix pack...?

A way around it would be to just have a 2-d cube with a static picklist of Jan through to Dec and reference that in your websheet. You could obviously use a TI to populate it with the "current" month as a starting point.

Or, on a similar note, have a TI run every morning creating a 'Current Month' subset with the single element representing the current month:

Code: Select all

# relies on elements in the Month dimension being JAN, FEB, MAR, etc
sCurrentMonth = TIMST ( NOW(), '\M' );
SubsetDestroy ( 'Month', 'Current Month' );
SubsetCreate ( 'Month', 'Current Month' );
SubsetElementInsert ( 'Month', 'Current Month', sCurrentMonth, 1 );

Then, instead of using:

Code: Select all

=TEXT(NOW(),"mmm")

You could use:

Code: Select all

=SUBNM("server:Month","Current Month",1)

Does that work?

[AmbPin]

Has anyone used FP3?
It seems there are many other things that now don't work, most seriously the ability to make modifications to some of our dimensions via the UI or TI. As soon as we touch some dimensions now the server crashes.
Think we will be going back a version.

[rmackenzie]

Has anyone used FP3?

Yes, and the release solved a number of important issues (for us, at least), and has been quite stable. It sounds like you have another problem in your setup beyond that of installing FP3.

[AmbPin]

Hello,

I am afraid I must draw a different conclusion, our model has been perfectly stable under 9.5.2.2.4 for quite some time and indeed on other servers it still is. It has only become unstable on the FP3 machines. I have been advised by our support company that we are not the only people to have been hit by this and that the issue has been reported to IBM.

[rmackenzie]

Sorry to hear that. If your system is crashing because of trying to use core functionality like updating a dimension, then this is a very serious issue.

I can't help wondering what release 9.5.2.2.4 is - is that 9.5.2 with Fix Pack 2 and Hot Fix 4 ?

[AmbPin]

is that 9.5.2 with Fix Pack 2 and Hot Fix 4 ?

Spot on.