Correct practice to develop data model : a separate model for each report vs one complex model

[tvaishnav]

I have to create a few reports that will be shared with everyone at the company. Data is currently stored in the company's ERP database. I am wondering what would be the correct approach to move further. I am going to use SSAS. Should I create a separate data model for each report? Or I should translate the transaction database of ERP to one single data model?  

I believe that creating a separate data model is easier since they will be less complex. However, I have to create a new data model each time I need a report. If I have one big model, I can use that for multiple reports. I believe maintenance would be difficult. Also, the model design will change based on the requirement. 

What is the correct practice?

[v-piga-msft · Accepted solution]

Hi @tvaishnav ,

Actually, we also could create the data model in power bi desktop.

When you load the data source in power bi desktop, Power BI Desktop makes creating those relationships easy, in most cases you won’t have to do anything, the Autodetect feature can do it for you. However, in some cases you might have to create relationships yourself, or you might need to make some changes to a relationship based on your requirement.

Please refer  to this docuement about how to create and manage your relationship in power bi desktop.

Best  Regards,

Cherry