Forum Discussion
Super UserHow to not remove Layout Diagram pbip project
Hi jaryszek,
Thank you for the follow-up question.
Yes, the report built on top of the newly created semantic model will see the data changes, as long as the semantic model itself is refreshed or reading updated data (for example via DirectLake/OneLake). From a data perspective, everything works as expected.What changes is only the model identity, not the data behavior. When you create or deploy a new semantic model, reports connected to that model will reflect the latest data, but Power BI treats it as a new model instance. Because of that, editor-specific elements like the model diagram layout don’t carry over, even though the report visuals continue to work normally.
Thanks again for using the Microsoft Fabric Community Forum.
Community SupportHi jaryszek,
Thanks for the follow-up question.
Yes, when you deploy or create a new copy of a semantic model, the metadata is always regenerated. Even if the model is created from the same definition, via deployment pipelines or REST APIs, Power BI treats it as a new semantic model instance, assigns new internal identifiers, and the diagram layout is reset as part of that process.
Deployment pipelines and REST APIs are meant for promoting or versioning semantic models, but they don’t preserve editor-specific artifacts like the model diagram layout. Any approach that creates a new semantic model (copy, deploy, rebind) will update metadata and drop the layout. If keeping the layout is important, the only reliable option today is to keep a single semantic model stable and change only the data behind it (for example using OneLake shortcuts). There’s currently no supported way to version semantic models and retain the diagram layout across versions.
Thanks again for using the Microsoft Fabric Community Forum.
Super UserOk, one more thing. So report build on top of newly created semantic model still will see the changes right?
- v-kpoloju-msft
Hi jaryszek,
Thank you for the follow-up question.
Yes, the report built on top of the newly created semantic model will see the data changes, as long as the semantic model itself is refreshed or reading updated data (for example via DirectLake/OneLake). From a data perspective, everything works as expected.What changes is only the model identity, not the data behavior. When you create or deploy a new semantic model, reports connected to that model will reflect the latest data, but Power BI treats it as a new model instance. Because of that, editor-specific elements like the model diagram layout don’t carry over, even though the report visuals continue to work normally.
Thanks again for using the Microsoft Fabric Community Forum.