TM1 Forum

Hi!

We have a problem with running processes from TM1 Web Application.

We have made few cubes, and posted it through Performance Modeler onto TM1 Web. Users should go to the Application on the web and fill cubes with data. There are few users, each responsible for part of the data (security is set so they can see only their subset of data).
Non admin user should be able to run the processes at every time that update dimensions, write necessary data into cubes and set security. Processes that update dimensions are not the problem but those that write (load) data into cubes are.

That user is not Data Admin and we don't want him to be. And that is our problem, if he is not data admin we don't know how to set everything so that he can still run data process.
When he runs it we get the error in log file saying that data reservation is required.
If we use function CubeDataReservationAcquire with his CAMID in every process, then he can load data without any error, but that is also something that is not great solution for us because if some of the users lock their part of the application, and the person in charge wants to run the process again he can't even though we have set this (it says that cell is not writeable).

Is there any other solution so that this error doesn't happen?

We were thinking of letting him run it through batch but then it says only that the batch is successfully called, but their is no message that says what happened with processes. We tried setting that batch writes message to log file for each process but were not able to put that log file to Web App (how can we put txt file to TM1 Web App?).
There is an option where we can write the data from log file to another cube but we would like to avoid additional cube and process, and just show the log file.

Hope everything I have written is more or less understandable and that someone can offer me a good solution

Thank you!

It would be hugely helpful if you could follow the Request for Assistance Guidelines and provide the actual code (even just the line that errors out) and the actual error message.

I am aware of this error message: "Cell is not editable: No Data Reservation". Is this the one you are getting or is it something else?

Hi

I assume you are talking about Contributor, which uses data reservation when taking ownership / releasing a node.

http://www.ibm.com/support/knowledgecen ... integrator

According to this article, if your TI tries to write to a cube that includes the the dimension of the Approval Hierarchy, then a user will be able to write to the cube only if he has the ownership.

So your options are the followings, without exactly knowing how your cube design looks like:
- and ADMIN can write to reserved cells
- try to write to a cube that does not have the approval hierarchy; as much as I remember such a cube is not included in the data reservation when you take ownership, release, or submit a node;
- do what you already tried: the TI should first take ownership, then write data, then release

if you let us know what your TI is intended to do, we may be able to help you further with other alternatives

mvaspal wrote: - try to write to a cube that does not have the approval hierarchy; as much as I remember such a cube is not included in the data reservation when you take ownership, release, or submit a node;

Cubes in which processes write in this case do not have approval hierarchy in them so we didn't have problem.

But we need to figure out what to do when there is approval hierarchy in cube in which we write (using CellPutS(N) or CellIncrementN).

mvaspal wrote: - and ADMIN can write to reserved cells
- do what you already tried: the TI should first take ownership, then write data, then release

Problem is when cells (some or all nodes) are locked.
When another user takes ownership of their node, writes in it and commits, that node is locked - as it should be. In that case, user who runs processes which load new actual data can not run them and he gets error saying that cell is not writable, no write access to element (error is not on English so we translated it).

qml wrote: I am aware of this error message: "Cell is not editable: No Data Reservation". Is this the one you are getting or is it something else?

This error we get when non admin user, who has right to run process, runs process that writes into cube with approval hierarchy in it (he can see all nodes). We can solve this using CubeDataReservationAcquire in every process that writes in cubes. Is there any other solution for this?

When nodes are locked, we get different message as I mentioned above where I quoted mvaspal.

if it's about loading actual data, you can load it to another cube and then write a rule to display actuals in the contributor cube.

mvaspal wrote:if it's about loading actual data, you can load it to another cube and then write a rule to display actuals in the contributor cube.

Yes, I know, but I am trying do avoid creating additional cubes.
Do you maybe know of any other, more elegant solution?

What mode are you using for data reservations? If you're using REQUIREDSHARED, then the TI should be able to obtain the necessary DRs regardless of whether other users have DRs on the same cells.

If this isn't working, what is the exact error message? It's very difficult to answer your questions when you don't provide specific details.

BrianL wrote:What mode are you using for data reservations? If you're using REQUIREDSHARED, then the TI should be able to obtain the necessary DRs regardless of whether other users have DRs on the same cells.

If this isn't working, what is the exact error message? It's very difficult to answer your questions when you don't provide specific details.

Yes, we tried using that mode and it is all the same.
One error is the one mentioned "Cell is not editable: No Data Reservation".

could you do following?

1) right click on process and check security access option

2) You can create a process based on parameter and design in to web so that when you run the process than node parameter would get select automatically. It means that now user is running process for his/her access only.

3) According to me, if you have applied point 1 than process would execute with data admin rights.