Forum Discussion
RLS To Impact only One Fact Table
One thing I can think of is to make a copy of the dimRoster and link it only to the factFraud table. Then you can apply the RLS to the copy of the dimRoster and it will flow only to the factFraud. You could make the dimRosterCopy really narrow so it only has the fields you need for the filtering and the relationship. You can also hide the table in the model so people don't see two dimRoster tables.
One thing I can think of is to make a copy of the dimRoster and link it only to the factFraud table. Then you can apply the RLS to the copy of the dimRoster and it will flow only to the factFraud. You could make the dimRosterCopy really narrow so it only has the fields you need for the filtering and the relationship. You can also hide the table in the model so people don't see two dimRoster tables.
Ah! This works. Perhaps not the cleanest solution, but it definitely works and doesn't seem to noticeably impact performance. Thanks!