Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
Our company has recently implemented the use of a single master data model so that all reports will have the same model, measures, calculated columns, etc. available. The use case is also as we update the master data model all reports will be updated together.
However we have noticed when publishing the reports built off of the master data model some of them appear to create their own dataset, however still linked to the master data model while others do not.
All reports to my knowledge have been built the same way by direct query connecting to the master data model via the data hub connection on the desktop. Is there possibly two paths here that I am choosing different thing without knowing it?
Does anyone know why this is happenning and how to stop it? It is causing some refresh issues for us.
See lineage below:
What can happen is that a user might connect via Analysis Services which then puts in the dataset, or it could be if the user clicked on Transform Data (which will then create a composite model which creates the dataset)
What happens if you open the PBIX do you see it as LiveConnection or DirectQuery?
The ones with the their own dataset are Direct Query.