Recalculate causing Unprotect Sheet Prompt - TM1 10.2.2

[MSidat]

Hi,

Just in the process of testing a TM1 Model in 10.2.2 (Win7, Excel 2010) and noticed that a recalc by way of either a F9 or a Tm1Recalc1 in VBA is causing the unprotect sheet dialogue box to come up when the sheet is protected. Cancelling the dialogue box enables the recalcs to occur as expected.

I have tested this in Excel with and without perspectives loaded (Only an issue when Perspectives is loaded, does not matter if you are logged into a server or not) and also with and without any TM1 Formulae on the sheet i.e. it even comes up on a blank protected sheet when the Perspectives Ribbon is loaded.

I note that this was previously an issue in 9.4 and possibly some versions of 9.5: http://www.tm1forum.com/viewtopic.php?p=12664

Just wondered if anyone else has come across this whilst testing 10.2.2.

Cheers

[declanr]

I can confirm that I get this same behaviour with TM1 10.2.2 and Excel 2013.
I only see it when the sheet is protected with a password and it seems to go through fine when it is protected without a password.

Luckily all my current users interface through web clients so protecting sheets without a password suffices for me, hence not having logged an issue with IBM yet.

[lotsaram]

Regression bug in 10.2.2
If it is acceptable you can protect the sheets without a password.
AFAIK logged already with IBM under the following codes.

Request:COGCQ00889340
Defect:COGCQ00889342
APAR:COGCQ00889343
APAR: PI23105

[MSidat]

Thanks for the info and confirmation guys. Ill get our resident expert Mr Vincent to chase IBM from our side.

[mail_kupi]

Hi All,

Did IBM respond on this issue?

[Steve Vincent]

Yes, ages ago they provided a fix. You'll need to look thru the release notes to find out which one it's covered by, i think its FP3

[kangkc]

I don't think it's included in FP3. Still happening under FP3. We have to use a blank password to bypass it for now.

[gtonkin]

FYI - there has been an APAR raised: PI45578
I cannot see any version impact information. Assuming that IBM would only have raised it if the client was on the latest version, should it have been corrected.