Page 1 of 1

Data level security in Cognos 10.1.1 reports - TM1 as data s

Posted: Fri Jun 08, 2012 4:59 pm
by Krish
I am using Cognos TM1 10.1 as a Data source for my cognos reports (10.1.1). I am facing difficulty to implement data level security in reports.

I am using .txt files to load the data into TM1 cubes. I have 2 reports.

1. Prompts Report
2. Main Report

I have merged these 2 reports in a page in cognos connection. When i run the page, left side prompts report and right side main report (data) will display and based on data changes in main report happens based on prompts selection.

I have filtered the prompts based on User login using user dimensions, but i am unable to filter the data page because user info is not available in data files which we are using for cube loading. so, in the dashboard page i am getting filtered prompt page but entire data page.

ex: If user 'A' logged in he can see only India and China prompt values in country prompt and related data only should be displayed in the data report, but my case user 'A' can see the right access on country prompt but all countries data in data report.

Here issue is we cannot extract the data files based on user.

So our data files do not have user info, but our dimensions have the user info.

Could anyone help to resolve this. Thanks.

Re: Data level security in Cognos 10.1.1 reports - TM1 as da

Posted: Fri Jun 08, 2012 11:48 pm
by PlanningDev
How exactly did you filter the prompt query? session parameters and manual mapping in a query item?
Are you using pass through authentication on the TM1 datasource with all of your security held inside TM1?

It sounds like you are trying to implement security in the report layer. It also sounds like your prompt values are not correctly filtering your report or whats happening is you are getting all data on report load but then it is filtered when a user makes a prompt selection.

One way to cover this is to not render that data if no prompt is selected. Maybe I have it wrong but sounds like what you are trying to do may be tricky to implement in the report layer by itself (and possibly the wrong approach).