Forum Discussion
Composite Model - Access Restrictions Problem
I have the same issue.
This seems like the key question:
"Does ‘not working’ refer only to the new tables in composite model?"
If the existing RLS is transferred, then it is a bit weird that there is no information about it here. But I hope it is. Did you get to test this on your data?
Indeed there is no information about any inherited RLS roles. The manage roles pane is blank:
You can only create the new roles, and only for a newly added tables (not from source model):
In the service, when getting into security option, there is such an information:
All in all, quite confusing.
Regards,
Dariusz
Hi Dariusz
Actually in our case, we have just finished a test of whether the RLS from the original is transferred despite the above message. And our test showed that it was.
So I believe the above message is just the one you get before you add any RLS. And we get it, because we have not added RLS in the tables that was added to the original dataset to create the composite model (we do not need RLS on those). But the message does not mean that the RLS from the original (main) dataset does not work for the composite model. It does.
They could give some more information, but in conclusion, it does actually work. So the answer to "Does ‘not working’ refer only to the new tables in [the] composite model?" is actually "Yes".That was also my conclusion based on the behavior of composite model I’ve got.
Regards,
Dariusz
Great. So the problem seems to be solved 🙂
Now our problem is just that if you make a composite model and the later update the main DirectQuery-connected dataset with e.g. new dimension, measures, etc., then those changes to the dataset is not transferred automatically to the composite model; and it seems there is no way to include them other than create the composite model from scratch again. I should ask this in a new thread, but if you have some experience about this, let me know. 🙂