Let's assumme that one group is allowed to see the content of a column and a other group isn't. If you simple only try todo use "permissions" the whole report will crash for the group which can't see the column.

You can workaround this crash with the "CHOOSE" statement. From the Oracle documentation:

First let's make a "No Access" column:

Drag the column somewhere in you presenmtation layer, be sure that the persmission is set to everyone. In your report edit the column which this group isn't allowed to see:

Now run the report again for the "No Access" group :

Till Next Time
2 comments:
Hi John,
this article http://obieeblog.wordpress.com/2009/01/15/obiee-data-security-column-level-security/ gives a more elegant solution to avoid the error message.
Regards,
Stijn
Hi Stijn,
You are right. I didn't know that feature. Thanks for sharing!
Regards John
Post a Comment