The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
Hi there -
I maintain two reports for two different-but-related audiences. The reports use the same data - however, one of the reports contains sensitive information and is therefore accessible to a more restricted group.
Initially, I maintained them as two different PBIX files with their own unique models. While it got the job done, it also created a continuous risk of human error - all it would take is for me to update one model but not the other for the figures to be out of sync.
So, I decided to instead publish the dataset and use it as the live source for the two separate reports. This worked great - until I discovered that in order for other users to see it, they apparently need to have Build permission (which I cannot give, due to confidentiality).
What would be the best way to manage the data model(s) with the least amount of maintenance and risk of human error? Ideally, I would like to have only one - but the Build permission requirement is a deal-breaker. I'd also be open to simply copying the models between the two reports - as long as there was a simply way to copy everything is bulk.
Solved! Go to Solution.
Hey @GeorgeCH ,
can you provide your end-result as an App to your audiences?
In my opinion the best way to give users easy access and you can create different audiences for different permission groups or other focus. RLS would also work within the App.
You will just need 2 reports (one for group 1, one for group 2).
Then you can make an App and create different audiences within the App.
We choose this way in our company to provide data.
Maybe a suitable trial for you.
Regards
Hey @GeorgeCH ,
can you provide your end-result as an App to your audiences?
In my opinion the best way to give users easy access and you can create different audiences for different permission groups or other focus. RLS would also work within the App.
You will just need 2 reports (one for group 1, one for group 2).
Then you can make an App and create different audiences within the App.
We choose this way in our company to provide data.
Maybe a suitable trial for you.
Regards
I think this would have been the best solution (and I'm therefore accepting it, for the benefit of future users).
Unfortunately, I don't have the license needed to create apps. As a result, I ended up having to copy-and-past the queries from one file to the other. It was less time-consuming than expected, although it still left me with the need to manually maintain the two datasets. Oh well!
Hmm, you don´t have permissions to create/update an App?
Why not? You are content creator...
You will need a Pro license (or PPU) and your role within the WS should be member or admin.
If you don´t have one of these roles WS admin can give you permission as contributor role to update the App.
Regards
Users shouldn't need Build permissions to see reports associated with a Report, they only need "Read". I have a report where I do not want users to see the Dataset, only the Reports associated with it, so they are a Workspace (of the report) Viewer and a Dataset Permissions "Read".
That being said, you may have opportunity to use Row Level Security. I've never had to and don't know much about it, but it's purpose is to limit what Data certain people see.
https://learn.microsoft.com/en-us/power-bi/enterprise/service-admin-rls
User | Count |
---|---|
37 | |
15 | |
12 | |
11 | |
8 |
User | Count |
---|---|
44 | |
42 | |
19 | |
19 | |
18 |