I have 20 reports that have a live connection to the same SSAS tabular model. Each report creates its own dataset in the service.
One of the best practices that I have heard over and over is to separate the data model from the report by first creating a dataset that doesn't have any visuals that provides the data model. Then in Power BI desktop, you need to change the data source in the report report to point to the dataset report. I have been through a couple video discussing the advantages of creating a Power BI dataset that I use as the data source for a report.
- Logic in one place; avoid managing logic in multiple files
- No proliferation of tabs, which avoids logic duplication by having one model/one report with each use case adding a tab
- No double refresh when two reports are added to the service with their own dataset
First issue: by using a live connection to SSAS, my logic resides in one place and when I change it, it proliferates to all reports. It doesn't matter whether I use one report with many tabs or multiple reports, the logic is still in one place. And the data only refreshes once.
The only theoretical (see next point) benefit to having one file is removing all of the datasets. It is a pain to have two objects with the same name in the list of Workspace objects.
Second issue: I can't find a way to take my 20 reports and change the datasource to a Power BI dataset. When try to change the datasource, I can change the server and database but nothing else. I can't change the provider. When I try to add a data source, everything is grayed out except Power BI Template Apps.
First of all, has anyone transfered their reports from a live connection to SSAS to one that has a Power BI dataset (that itself has the live connection to SSAS)? Second, what advantages are there to separating the dataset from the report in this case.
