Unable to commit data: staying blue

Ideas and tips for enhancing your TM1 application
Post Reply
User avatar
ioscat
Regular Participant
Posts: 209
Joined: Tue Jul 10, 2012 8:26 am
OLAP Product: Contributor
Version: 9.5.2 10.1.1 10.2
Excel Version: 07+10+13
Contact:

Unable to commit data: staying blue

Post by ioscat » Fri Aug 03, 2012 11:37 am

It seems to be a kind of trick. Maybe this will help you someday.

Preblem example discribed here and here
We have two versions of budget A & B (two elements of dimension), and firstly A was completed by users and security status was set to 'READ'. But some of data was not commited (users see it as blue). This led to data in version B became uncommitable - always staying blue.

The solution is:
1) Unblock A version;
2) Recommit A version;
3) Block A version;
4) Commit B version
5) ..?
6) Profit

P.S. I would like admins to correct my post to make it clearer to understand and find by web search. Please.

User avatar
ioscat
Regular Participant
Posts: 209
Joined: Tue Jul 10, 2012 8:26 am
OLAP Product: Contributor
Version: 9.5.2 10.1.1 10.2
Excel Version: 07+10+13
Contact:

Re: Unable to commit data: staying blue

Post by ioscat » Thu Nov 15, 2012 3:05 am

maybe someday this will help someone.

We developed cube and put a form to application. Users have put their numbers in it. And after that we decided to create rule on some cells.
This will result in 1) change data in cell, 2) cell become read only, 3) users data in his sandbox remain blue and non-commitable.
How to avoid 3-rd point? We decided to 1) delete element of dimension that will not have user data, only calculated, 2) add it back.
With first operation all blue data in users sandbox will sink at Lethe.

TM1 9.5.2

Post Reply