Forum Discussion
Datasets - one large or many small
Community ChampionIt may be a combination. You could have one big dataset with most or perhaps all of the data, and then share that dataset to the otehr departments. You can then restrict what they can and cannot do/see. So your primary data set can have Sales, but you don't expose Sales to the Engineering team for example. You need to have the new Gen2 workspaces to do this, so if you have Gen1, click the little upgrade button in the workspace settings.
There is no perfect solution to your issue - it is all about optimization, not perfection. Share Datasets has been a HUGE boon for me in this processes, but there are still times I completely segregate data and datasets. That, and I've not pulled the trigger on upgrading all of our workspaces to the new Gen2 type yet.
Yes, several departments uses the same kind of data.
However, RLS feels a little bit weird. When people open up the reports and just see blanks on one page?
But I think I will go back from multiple datasets to two datasets. Just a mess to keep track on measures and changes in measures between datasets.
Thank you so much to both of you!
Hi,
One thing you could do to customize reports for different departments but still use a common data model is to publish the report + model to the Power BI Service. Then you create a new report and connect it to the dataset in the service:
Best Regards
Ulf
Yes, but that still requires one BIG dataset, which means the reports will still be a bit slow compared to smaller ones.
But I guess it's all a matter of a balance. Can't have both.