Forum Discussion
Report from composite semantic model not working after workspace name change
- 1 month ago
As far as i know this is a known limitation of Power BI composite models (Direct Query to Power BI semantic models).
The outer semantic model retains a reference to the original workspace metadata. As a consequence, renaming or moving the workspace can break the Direct Query connection. Returning the workspace name restores the connection because the original reference becomes valid again.
Unfortunately, based on my research there is currently no supported way to repoint an existing outer semantic model to a different workspace or semantic model. The recommended solution is to remove and recreate the Direct Query connection, then republish the outer semantic model.
If this helps, ✓ Mark as Kudos | Help Others
As far as i know this is a known limitation of Power BI composite models (Direct Query to Power BI semantic models).
The outer semantic model retains a reference to the original workspace metadata. As a consequence, renaming or moving the workspace can break the Direct Query connection. Returning the workspace name restores the connection because the original reference becomes valid again.
Unfortunately, based on my research there is currently no supported way to repoint an existing outer semantic model to a different workspace or semantic model. The recommended solution is to remove and recreate the Direct Query connection, then republish the outer semantic model.
If this helps, ✓ Mark as Kudos | Help Others