Hi All,
I've been asked to come up with a solution for allowing non-admin user the ability to run some data load TI processes. My preferred solution was to use a websheet and action buttons. I've set this up and the loads work OK for me as an admin user through Contributor.
The websheet is published to a Central application. The cube being loaded into is in a separate workflow application that also has a control dimension in place.
When a non-admin user clicks the action button the process fails. I can see from the log that it is triggered correctly so I think that user has sufficient access to execute the process.
Data Source line (1) Error: Data procedure line (4): A Pre-existing data reservation is required before performing an update to Cube "CUBENAME".
The process loads data from a SQL datasource and uses a parameter to restrict the data returned from database. This parameter is referenced in a cell on the worksheet next to the action button so the user can specify with data to load. I have a secondary process that is called from the prolog (using ExecuteProcess function) that zeros out all necessary data that is about to be loaded/reloaded. This prolog process executes correctly for the user.
Has anyone come across this error message or successfully implemented a scenario like this?
Regards,
Chris
Non Admin User Running Action Button Process
-
- Posts: 4
- Joined: Wed Aug 19, 2015 2:03 pm
- OLAP Product: Cognos BI
- Version: 10-2-0 64bit
- Excel Version: 2010
Re: Non Admin User Running Action Button Process
Update: The user decided to take ownership of one the workflow application nodes and then tried to load data into that node. This was successful.
Is there a good way to allow the user (through a group) to force data into the cube even if they don't have ownership of the node in the workflow application?
Regards,
Chris
Is there a good way to allow the user (through a group) to force data into the cube even if they don't have ownership of the node in the workflow application?
Regards,
Chris
-
- MVP
- Posts: 264
- Joined: Mon Nov 03, 2014 8:23 pm
- OLAP Product: TM1
- Version: 9.5.2 10.1 10.2 PA2
- Excel Version: 2016
Re: Non Admin User Running Action Button Process
You're getting the error because the "DATARESERVATIONMODE" cube property is specified as "REQUIRED".
http://www-01.ibm.com/support/knowledge ... ataresmode
Unfortunately, changing this setting is a potentially blocking operation on the cube, even if just using CellPutS in the prolog and resetting the value back in the epilog.
You could also try adding code to the TI to grab the required data reservation. There are TI functions for this documented here
http://www-01.ibm.com/support/knowledge ... ataresmode
Unfortunately, changing this setting is a potentially blocking operation on the cube, even if just using CellPutS in the prolog and resetting the value back in the epilog.
You could also try adding code to the TI to grab the required data reservation. There are TI functions for this documented here
-
- Community Contributor
- Posts: 341
- Joined: Wed Nov 03, 2010 9:16 pm
- OLAP Product: tm1
- Version: 10 2 2 - 2.0.5
- Excel Version: From 2007 to 2013
- Location: Earth
Re: Non Admin User Running Action Button Process
Hi,
I am not sure if in 10.2 or 10.2.2 it was introduced but TIs (and admins manually) can now load/enter data to reserved cells and so if your non-admin user is allowed to run the TI then he should be able to load data to a reserved cell. If you are not on this version of TM1 yet, you will need to get the reservation for the user.
Or option B: load data to another cube and write a rule to the Contributor cube - this works if the data they are trying to import is just for reporting and should not be overwritten in Contributor
I am not sure if in 10.2 or 10.2.2 it was introduced but TIs (and admins manually) can now load/enter data to reserved cells and so if your non-admin user is allowed to run the TI then he should be able to load data to a reserved cell. If you are not on this version of TM1 yet, you will need to get the reservation for the user.
Or option B: load data to another cube and write a rule to the Contributor cube - this works if the data they are trying to import is just for reporting and should not be overwritten in Contributor