We have created a Dashboard using a Data module.
We have created a variable which will store the session user id(login id).
Using this variable we have created a filter to apply row level security.
We have used this security filter in each "Local filter" field of the visualization.
But we have noticed that user is able to hover on the filter and delete this filter. Kindly suggest a way in which we can restrict end user from deleting this pre-defined filter or any alternative way to apply row level security to Dashboards created using Data module.
Without knowing what your filter is, presumably an expression of some sort, if you incorporate the filter into the objects in the module that would encapsulate the security filters and thus hide it from people. In 11.1.x you can set up filter expressions in addition to filters on columns.
Just to confirm, you're working with files rather than a data base, which is why you have not set the data security on the data base schema in the module. (another 11.1.x feature)
Another approach would be to set the dashboard to be read only but that has drawbacks.
Quote from: vaibhav.pujari89 on 15 Jul 2020 09:55:34 AM
We have created a Dashboard using a Data module.
We have created a variable which will store the session user id(login id).
Using this variable we have created a filter to apply row level security.
We have used this security filter in each "Local filter" field of the visualization.
But we have noticed that user is able to hover on the filter and delete this filter. Kindly suggest a way in which we can restrict end user from deleting this pre-defined filter or any alternative way to apply row level security to Dashboards created using Data module.
Hi,
The way to lock this down is to define the security in the data module rather than in each dashboard. Assuming you are using 11.1.x (not 11.0.x) you can set up filters based on user/group etc in the data module:
https://www.ibm.com/support/knowledgecenter/SSEP7J_11.1.0/com.ibm.swg.ba.cognos.ca_mdlg.doc/t_ca_mdlg_secure_data.html
Cheers!
MF.
Thanks MF.
Applied the changes as deccribed in link. Its working fine now.