Forum Discussion
Shared Dataset and Composite Dataset
Hi
What is your opinion on using Composite models.
I am trying to define a model for one of the projects. We plan to build SAP model based on SAP Module specific tables. As and when common KPIs are identified, they are added to main dataset. If there are some KPI needs from specific business which only they want to see or utilize, KPI table will be created and they will use the main model + KPI table for that specific business.
But the problem is
1. Composite model is not in GA.
2. We do not want to duplicate the same data model in multiple workspaces (duplicating same data for different reports)
3. Other challenge still remains, we load raw data with common links between SAP tables to PowerBI. Data volume is huge and incremental does not work as intended as many tables in SAP do not have date columns.
Any help is highly appreciated for the 3 pain points
3 Replies
Hi ddfreedie
What I would do is to create a single dataset and host that in an App Workspace just for the dataset. This will allow you to have a single dataset to add KPIs to etc. This will also mean you only have to update a single datset.
To your questions
1. I think soon Composite models will be GA
2. Suggestion above to create a single dataset and then connect reports to this dataset.
3. I would see if there is a way to aggregate any of the SAP data so that is a bit smaller and easier to manage?
Hi
Thanks for your reply.
We have done a couple of projects with that approach. Have DS in one workspace and reports in their own workspace and some reports with excels + shared dataset as composite models.
1. I do not see GA plans for composite model in PBI release plan until sep 2022. So not sure.
2. Yes that has been the idea. To create common dataset and use it as much as possible for all common KPIs. If some additional depertment specific KPIs are needed, to have composite model
3. Unfortunately most of the use cases need transaction data at the detail level. The volume of data is huge. So we plan to create models with transaction + master data (dimensions) and have common/global KPI table/views joined to the model itself. But wondering if anyone has faced similar issue/idea in designing SAP models in PBI.
Hi ddfreedie
Yeah it might be a bit of time but I think it is save to say it will go GA!
With regards to your transaction level detail I would have an aggregated table and then a directquery table which they can use to drill through to the underlying data, which will also pass through the filters so it will only be a subset of the data.
