This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
Hello, Team.
I have a report published to one workspace which is created with live connection to a semantic model published in another workspace.
This report is in the production workspace and refers to a model in the development workspace, however all reports in the production workspace should only refer to models in the production workspace.
I'd want to update the model to which this report refers; to do so, I downloaded the report from the service in live connection mode and opened it in desktop. I changed the model from development to production, as referred to in this report, and published the report again in the same workspace. While publishing, the replace option is not displayed, and the report is duplicated.
I'd like to know if this is the expected behavior or if there is something I'm missing.
Solved! Go to Solution.
Hi @Pawan_123, Hope you are doing good !
This can happen due to several reasons:
Dataset and Report Relationship: Power BI distinguishes between datasets and reports. When you change the dataset to which a report is connected, Power BI may treat the report as a new entity, especially if the dataset resides in a different workspace.
GUIDs and Identifiers: Each dataset and report in Power BI is identified by a unique GUID. When you change the dataset (even if the schema and data are identical), the report's connection to the dataset might be considered a different object.
Did I answer your question? Mark my post as a solution! Appreciate your Kudos !
Hi @Pawan_123, Hope you are doing good !
This can happen due to several reasons:
Dataset and Report Relationship: Power BI distinguishes between datasets and reports. When you change the dataset to which a report is connected, Power BI may treat the report as a new entity, especially if the dataset resides in a different workspace.
GUIDs and Identifiers: Each dataset and report in Power BI is identified by a unique GUID. When you change the dataset (even if the schema and data are identical), the report's connection to the dataset might be considered a different object.
Did I answer your question? Mark my post as a solution! Appreciate your Kudos !
yes, this behaviour is expected. two reports with different "data source names" can have the "same report name" in the same workspace. Since there is no new dataset created with Live connection, two reports can have the same name. This is obviously confusing and should be avoided, but it has always been allowed.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 11 | |
| 10 | |
| 7 | |
| 7 | |
| 6 |
| User | Count |
|---|---|
| 28 | |
| 25 | |
| 22 | |
| 22 | |
| 19 |