Forum Discussion
Advocate IISelective report sharing within an organization
rode One centralized model to support many reports is absolutely the best way to go. The vast majority of my recomended solutions revolve around implementing a single/few tabular models for scaling out corporate reporting efforts. This also gives you the ability to use the Live Connection and removes the need to manage refresh schedules.
Advocate IIHi Anonymous and thank you for your reply.
I don't think that this is the right solution: I already use RLS, but it allows the users to see a piece of data. They cannot deny a user to see a specific piece of report (that's my need!).
Thanks,
Regards.
rode You are correct. I missed the key piece.
My thoughts are this, as there is no way to conditionally hide report pages themselves.
I would break out the reports into seperate pieces.
The main piece would be a single report that has all the common or shared parts for all the groups.
Then individual reports for each group
This would remove any potential duplication of report pages and be easier to manage down the road.
I wouldn't go the Content Pack route as those are eventually being deprecated. And I don't see how that resolves the issue. App workspaces / sharing apps would be the new way to share out content.
- rode
The key problem here is measure definition: I don't want to define a measure as many times as the number of sections. In order to achieve this aspect the solution that I see is to migrate the dataset to Analysis Services Tabular Model in order to use DAX on that and import it directly into Power BI reports (that of course will share the same dataset as well).
Anonymous do you agree?
Thanks!!!
rode One centralized model to support many reports is absolutely the best way to go. The vast majority of my recomended solutions revolve around implementing a single/few tabular models for scaling out corporate reporting efforts. This also gives you the ability to use the Live Connection and removes the need to manage refresh schedules.