Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Reply
NewUser777
Resolver I
Resolver I

Why cant one workspace be used for data models and reports in advanced data model management ?

Why cant one  workspace   be used for data models and reports in advanced data model management usage scenario ? Why do we need two separate workspaces - one for reports and one for datasets assuming it is a Development envirorment for content creators( Report builders and Data model developers)?

 

advanced data model management usage scenario explained here -

https://learn.microsoft.com/en-us/power-bi/guidance/powerbi-implementation-planning-usage-scenario-a...

 

This scenario focuses on decoupling the model development process from the report creation process.

 

 

 

3 REPLIES 3
ichavarria
Solution Specialist
Solution Specialist

Hi @NewUser777,

 

In an advanced data model management scenario, it is recommended to separate the development of data models from the creation of reports. This separation is beneficial for several reasons:

 

  1. Data model development involves creating complex calculations and relationships that can be time-consuming and require careful planning. Separating this process from report creation allows for more efficient development as the data model can be iteratively refined without affecting reports.

  2. Separating the data model development process from report creation also allows for better collaboration between data model developers and report creators. Data model developers can focus on creating a robust data model that meets the business needs, while report creators can focus on creating visually appealing and informative reports.

  3. It also allows for better version control and change management. If the data model and reports are developed in the same workspace, changes made to the data model can inadvertently affect the reports, leading to errors or inconsistencies. By separating the two, changes made to the data model can be tested and validated independently of the reports.

  4. Finally, separating the data model development process from report creation can help ensure that reports are based on accurate and reliable data. This is because the data model can be validated and tested before it is used to create reports, reducing the likelihood of errors or inaccuracies in the final reports.

 

Therefore, having separate workspaces for data model development and report creation can help ensure more efficient, accurate, and reliable data modeling and reporting processes.

 

 

Best regards, 

Isaac Chavarria

If this post helps, then please consider Accepting it as the solution and giving Kudos to help the other members find it more quickly


@ichavarria wrote:

Hi @NewUser777,

 

In an advanced data model management scenario, it is recommended to separate the development of data models from the creation of reports. This separation is beneficial for several reasons:

 

  1. Data model development involves creating complex calculations and relationships that can be time-consuming and require careful planning. Separating this process from report creation allows for more efficient development as the data model can be iteratively refined without affecting reports.

  2. Separating the data model development process from report creation also allows for better collaboration between data model developers and report creators. Data model developers can focus on creating a robust data model that meets the business needs, while report creators can focus on creating visually appealing and informative reports.

  3. It also allows for better version control and change management. If the data model and reports are developed in the same workspace, changes made to the data model can inadvertently affect the reports, leading to errors or inconsistencies. By separating the two, changes made to the data model can be tested and validated independently of the reports.

  4. Finally, separating the data model development process from report creation can help ensure that reports are based on accurate and reliable data. This is because the data model can be validated and tested before it is used to create reports, reducing the likelihood of errors or inaccuracies in the final reports.

 

Therefore, having separate workspaces for data model development and report creation can help ensure more efficient, accurate, and reliable data modeling and reporting processes.

 

 

Best regards, 

Isaac Chavarria

If this post helps, then please consider Accepting it as the solution and giving Kudos to help the other members find it more quickly


Data model any how is connected to reports which are sourcing the data from the data model using live connection .  So if they report content and dataset content are present in single workspace or other workspace its still the same effect .

Scenario 1 : All content in same workspace

Example:  X report and Y report  is pointed to A data model in the same workspace .

 

Scenario 2 : All content in different workspace

Example:  X report and Y report  are in different workspace and is pointed to A data model in the different workspace .

 

@ichavarria I think the real reason is content sharing .

@ichavarria Do you agree with my previous post  ?

Helpful resources

Announcements
April AMA free

Microsoft Fabric AMA Livestream

Join us Tuesday, April 09, 9:00 – 10:00 AM PST for a live, expert-led Q&A session on all things Microsoft Fabric!

March Fabric Community Update

Fabric Community Update - March 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors