Issue with TM1 Security via TI though Perspectives

[LanceTylor]

Hi All,

I am using Cognos express 9.5

I am having a problem updating element security rights for groups via TM1(Xcelarator) Perspectives through TI process. I created a process(s) below to populate the "Element Security Version Cube".

Process Info
1. Parameters are set up to capture the "Element" and the "Security Level (Ex: Read).
2. The Process uses the }Groups dimension subset to capture "All Groups" this is an MDX subset ("Subset All")
3. In the Data Tab I have the TI scripts (shown below) which should populate the "Element Version Security Cube"

The process works when i run it in Architect and fill in the Parameters but when i try it in MS Perspectives via an action button it doesn't populate the anything but indicates that the process was sucessful???

Process Details
SecurityCube='}ElementSecurity_Version';
DimName='Version';
pSecurityRights = 'Read';
pElement = 'Actual';
SecurityGroups = MDX subset from the }Groups Dimension

Trial 1
CellPutS(pSecurityRights,SecurityCube,pElement,SecurityGroups);

Trial 2
ElementSecurityPut(pSecurityRights, DimName, pElement, SecurityGroups);

As Always, any suggestions would be helpful

Lance

[Martin Ryan]

The process works when i run it in Architect and fill in the Parameters but when i try it in MS Perspectives via an action button it doesn't populate the anything but indicates that the process was sucessful???

When you say that it indicates the process was successful do you mean the action button resulted in a message box saying it ran ok? If that's what you mean then take a look in the message log (right click on the server in perspectives and click "View message log...") that will tell you whether the process was actually run on the server and what the outcome was.

That will help you tie down whether the problem is the process, or the action button, because it sounds to me like the problem might be the action button, not the TI process.

[declanr]

Notice that your info states you are using Excel 2007.

Something quirky about 2007 is that should you create a top notch sheet that has an Action Button run a process - which finds parameters through cell references... it will work until you close the workbook and open it up again at which point if you open said action button you will see that Excel/TM1 has somehow merged the 2 parameters into 1 uber reference that just does nothing ...

If that is the case for yourself, try re-creating the book/sheet but save it as a 2003 compatible blah blah blah book and it should sort itself out.

[tomok]

When you run a Ti process that includes parameters through Architect it will prompt you to key them in. When you run a TI via an action button, you have to reference each of the parameters in a cell somewhere in the workbook. Are you certain you did this correctly? For example, does the pSecurityRights reference look something like:

=A1
or
=NamedRange

????

[LanceTylor]

Martin,

Just check the Message Log and its seems like its working but no values? I have even included "Security Refresh" in the Eplog
41412 INFO 2012-04-26 20:39:45.148 TM1.Process Process "Security - VersionDim": finished executing normally, elapsed time 8.36 seconds

Declanr,
I have had fun with that in previous projects. On this project, I haven't encountered that yet and I have several process I built for endusers over the web

I find these issues come up especially when deadlines are tight.....I love consulting.

[Martin Ryan]

Ok, so the process is getting run ok. Next step is to put debug information in the TI process. Just spit some stuff out using asciioutput - my first stop would be exporting all the parameters that are getting passed in. One of them must not be what you expect.

[LanceTylor]

The parameters are using the correct sheet and cell reference.

I will try the debug and see what happens.....be in touch shortly.

thanks for the suggestions

Lance

[LanceTylor]

One last point I forgot to include.

The cells the parameters are referencing are (1) SubNm formula for the "Version" (2) An excel validation list for the Security Level "Read"

Back to the debug process