Unable to select elements in subset editor

[lotsaram]

I'm sure someone out there will have seen this before and know the root cause of the problem and have a solution. I was hoping even to be able to find it posted here but unfortunately the search terms are too generic and didn't turn up anything useful.

I have a user who's TM1 client is working perfectly normally (9.5.1 with XL 2010 on Win XP) in terms of slice OK, update data OK, double-click SUBNM launches subset editor. But in the subset editor the user is unable to select any elements in the left hand panel. All other aspects of subset editor work normally, sort, filter, etc. but nothing happens when elements are clicked to select. This renders assisted navigation to change the value of a SUBNM in an Excel report fairly useless.

So far tried: restarting Excel, restarting PC, deleting subed.tbd,
None of which worked.

No other users of several hundred have this issue so it must be something PC specific and it just started today.

There must be a silver bullet for this. Who knows what it is?

[Paul Segal]

I've come across this when using odd combinations of other software (for me a combination of Synergy and RDP). I would check what else is on the PC.

Regards

[declanr]

I remember having something similar to this a couple of years ago and it seemed to be a result of not having "Allow editing directly in cells" selected.

[lotsaram]

I've come across this when using odd combinations of other software (for me a combination of Synergy and RDP). I would check what else is on the PC.

I thought that but user swears they haven't installed anything recently.

I remember having something similar to this a couple of years ago and it seemed to be a result of not having "Allow editing directly in cells" selected.

Tried that. But anyway the problem is also there when subset editor launched from cube viewer or dimension tree when Excel is not even in the picture. It is a subset editor issue as opposed to anything else.

[stephen waters]

No other users of several hundred have this issue so it must be something PC specific and it just started today.

Lotsa, You've probably already thought of this but just in case. In the past we have had display problems caused by odd saved settings in the tm1p.ini file, which would make sense if it is only one user affected. Deleting tm1p.ini would cure it.