Hi @AlexEncuble ,
Thanks for reaching out to the Microsoft fabric community forum.
Here are some possible reasons for the issue you're experiencing, as well as steps to address it:
Potential Causes:
Data Source Configuration Mismatch:
Ensure the new Semantic Model data source is configured correctly and matches the one that was previously used. Sometimes, a minor discrepancy in connection settings can prevent it from updating properly.
Semantic Model Versioning or Caching:
If the new model isn't being recognized as an update but as a separate entity, there might be a versioning issue or cache that’s causing confusion. This can also happen if you're using a new connection string or endpoint that isn't recognized as the same model.
Power BI Service Data Source Refresh:
The Power BI Service might be caching the connection settings or not recognizing the new model due to a data refresh delay or configuration mismatch.
Report Duplication Behavior:
Power BI typically creates a duplicate report if there is an issue with the new data source being linked correctly, or if Power BI doesn't recognize it as the same model, as a safety measure.
Steps to Resolve:
Verify Data Source Connection:
Check the new Semantic Model connection string and ensure it's pointing to the updated cube. Compare this with the previous configuration and make sure they align.
If you're using Power BI Desktop, make sure the data source connection matches the same settings that worked in your tests. After this, publish the updated report back to the Power BI Service.
Clear Cache:
In the Power BI Service, try clearing the dataset cache to ensure that you're pulling the latest version of the model. This may solve issues where Power BI is still pointing to the old model due to cached data.
You can also try refreshing the dataset manually and see if it picks up the new Semantic Model.
Repointing the Report to the New Model:
If you're still seeing the old report alongside the new one, try removing the old data source from the report and reassigning the new Semantic Model data source explicitly. This might help Power BI recognize the change.
Alternatively, delete the old report and re-create it by linking it to the new model.
Update the Existing Report:
If you don’t want to reshare all reports, make sure the semantic model’s new data source is reflected in the report and dataset properties. After the update, republish the report without changing its name, so users retain access to it without needing to reshare.
Check permissions as well: Sometimes, old permissions or connections prevent the new Semantic Model from being adopted successfully.
Check for Dataset Dependencies:
If there are dependencies (e.g., shared datasets) in place, you might need to update these references in the Power BI Service manually.
It could be helpful to disconnect and reconnect these dependencies to ensure they're pointing to the new model.
Test in a New Workspace:
As a last resort, consider creating a test workspace and publishing the new report with the updated Semantic Model there. If it works, you can move the report over to the production workspace, ensuring minimal disruption to the users.
If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS. Feel free to reach out if you need further assistance.
Thanks and Regards
