Forum Discussion
Report from composite semantic model not working after workspace name change
Hi,
Data consumers reported an issue in a report pointing to data access issues. The report was built on the "outer" semantic model of composite. At the moment of the error, the outer and the inner semantic model were living in the same workspace.
The issue, was that the workspace changed its "description".
We saw, the connection of the direct query in the outer semantic model was still pointing to the original workspace name. We tried to change it manually, by renaming the direction, but the issue persisted.
We reverted the workspace name to the original one, and the error was resolved.
Is there any way to repoint the outer semantic model to a new connection, or how can we correct the connection without rebuilding the semantic model again?
Thank you if anyone can help
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
3 Replies
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 OthersThankyou Murtaza_Ghafoor for Addressing the issue.
Hi HITBI01 ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
Regards,
Chaithanya
Hi, v-kathullac
yes, it help to confirm the suspected behaviour.
Unfortunately it is a pitty you can not actually repoint the semantic model.Thanks in any case
