Author Topic: FM Security  (Read 152 times)

Offline cognos05

  • Statesman
  • ******
  • Join Date: Apr 2014
  • Posts: 706
  • Forum Citizenship: +1/-1
FM Security
« on: 23 Sep 2020 09:19:38 pm »
Hi ,

I have mostly been building cubes in transoformer and using custom views for security .
I wanted to understand if whats the right place to define security for a fm model having a star schema .

Assume  I have dimensions like product and customer and a fact table sales .

So i have this customer table having customers belonging to different regions and areas.

so now if i define the security on customer table , will it show all records in the fact if the customer is not used in the query and if just product and sales are used?

so any row level filters has to be done only on fact table ?

If we define the row level security on a fact table , then can users see all the values of customer table ?

so how does this concept work here , should we maintain security on both places?

Example say i have to create a group who can see only customers sales from region1 , so should i now filter the fact for this group with region1 or should i filter the query subject customer with value for region1 .

Any suggestions is appreciated.

Thanks,

Online bus_pass_man

  • Statesman
  • ******
  • Join Date: May 2008
  • Posts: 435
  • Forum Citizenship: +43/-0
Re: FM Security
« Reply #1 on: 24 Sep 2020 06:38:38 am »
I ended up creating the security filters on both the fact tables -- to ensure that all queries would be filtered to only show the values allowed, no matter whether a particular dimension which has a security filter is in the query or not -- as well as the dimension tables.  It produces duplications of the filter but if there is a magic way to do it otherwise, I have not seen it documented.