Hi Jo Marie,
Security is applied to the Data Source, thus when you create a security filter against this table it will always be applied. That is for direct references as well as views, joined views etc.
If a table needs to be used with both security turned on as well as not secured, then creating a view in the database is a good solution. Then secure only one of the two table objects in the Data Source using the Web-based modeling tool.
When you create a security filter it is possible to reference another table (from CA 11.1.3 and up)
For example securing the ORDER_DETAILS table with a filter :
ORDER_NUMBER IN (CASE WHEN ORDER_HEADER.ORDER_METHOD_CODE = 2 THEN ORDER_HEADER.ORDER_NUMBER END)
//Henk
------------------------------
HENK CAZEMIER
------------------------------
Original Message:
Sent: Fri August 23, 2019 02:16 AM
From: Dmitriy Zats
Subject: Data Module question about table that needs security and doesn't
You are correct. Aliases don't carry over security from the parent objects. What security method have you implemented? Parameter Maps?
Dmitriy
Original Message------
I have a fact table that has an institution key and source institution key. The institution key needs security and the source institution key doesn't.
I have applied security for the table that is joined to the institution key. If I add another copy of the institution table is the security that was applied going to apply to it also? I am kind thinking it will.
One way to get around this that I can think of is to not join the source institution key to another institution table. But then I can't get to information like the institution name or institution type.
In Framework manager, make 2 queries of the database table and apply security to one and not the other.
Only other way would be to create a view in the database call source institution that is based on Institution and not apply the security there.
Any other ideas?
------------------------------
Jo Marie Sellner
------------------------------
#CognosAnalyticswithWatson