Active form not showing correct value until pressing enter

[craig_karr]

I have an active form using the TM1TPTROW formula to drill down on the projects (rows). One of the columns is not showing the correct value until I put the cursor on the cell that has the wrong value (to check the references of the cell) and the pressing enter. Then the correct values hows up but when I recalculate the sheet the value disappears again. I find this very odd and wonder what the reason could be

[craig_karr]

It seems like the column I have trouble with is using another title element for one of the dimensions, compared to the other columns. Is this a problem with active forms? If so is there any good work around to handle the issue?

[lotsaram]

If you have inserted additional columns or changed context filters for your misbehaving column then you may find the answer here http://forums.olapforums.com/viewtopic. ... 912#p14853

[craig_karr]

Thanks! Solved the issue perfectly!

[Jeroen Eynikel]

I have a very similar issue, but not with active forms.

I.e. we are testing an upgrade to version 9.5.1 (coming from 9.1) and the excel reports don't refresh properly untill you have gone into an individual cell and 'entered' it. From then on that cell will refresh properly again. (If not it will either be stuck on RECALC or it will just show the old value again)

This is not really a workable solution as a. the number of reports that would needto be modified is huge. b. it is not exactly confidence inspiring as it does not give me the feeling that I can be certain that the problem will not reoccur.

Anyone seen this before?

[Alan Kirk]

I have a very similar issue, but not with active forms.

I.e. we are testing an upgrade to version 9.5.1 (coming from 9.1) and the excel reports don't refresh properly untill you have gone into an individual cell and 'entered' it. From then on that cell will refresh properly again. (If not it will either be stuck on RECALC or it will just show the old value again)

This is not really a workable solution as a. the number of reports that would needto be modified is huge. b. it is not exactly confidence inspiring as it does not give me the feeling that I can be certain that the problem will not reoccur.

Anyone seen this before?

Not something specific to TM1 reports, but I've seen this sort of thing in general Excel workbooks when the calculation dependency tree gets borked in that workbook. [Ctrl]+[Shift]+[Alt]+[F9] will do a full calculation, and also rebuild the workbook's calculation dependency tree. If it's happening in every workbook that's not likely to be the issue, but if it's only some of them it's worth a shot.

[Jeroen Eynikel]

I think I found the solution. We're still testing to make 100% sure but in this case it seems installing SP2 of office 2007 resolves the issue.