TM1 Forum

Hi vinnusea, you can also use Approval Hierarchy to control your users' access to the data (if you use TM1 Contributor). Using a very simple Approval Hierarchy, each user/group is assigned to a separate node in the approval hierarchy. Let them open the node and play with data. In the end, copy the &...

Hi lpahnke, If I were you, I wouldn't bother changing cube/element securities for this bug at all. I already verified with IBM Tech Support, he told me you don't need write access to those cells indirectly affected by contributor data entry. It is ridiculous if they designed things this way (you nee...

We are on 9.5.2 FP2 (with no hot fix). Windows 2008 R2, Cognos BI 10.1 We are having the same issue here, and our situation, seems, is supporting mtraskel's "multiple user" theory. We can re-arrange user access to limit one user to any node, plus the Reset Data, but, I just hope IBM can fi...

We are still working with IBM tech support on this issue. I just verified with the IBM guy -- that is not true -- you need to have write access to all cells which will be updated by the data commit. This might be a workaround for now, but, in my opinion, this is horrible application design if it's t...

We are having the same issue here. Very frustrating. TM1 Contributor users have entered data but can’t COMMIT in the system. During this struggle, they’ve lost their work, sometimes several days worth of work.

We had this issue last month (before FP2), and we installed FP2, but still sees this issue yesterday and today. (we use 9.5.2 with Cognos BI 10.1 security). Symptom is intermittent and happens on about 1/10 of our Contributor users. The main symptom is - user took ownership, entered data, can't comm...