Git Integration report cross workspaces

Hi David

This is a known limitation with Fabric Git integration — it only works with items in the same workspace, so a report pointing to a semantic model in another workspace just can't be committed through the UI.
The typical workaround is to keep the report and semantic model in the same workspace and use deployment pipelines to move them across environments. The pipeline handles rebinding automatically.
If separating them is a hard requirement, you're looking at managing it manually via the REST API, but that's pretty painful compared to native Git integration.

Hi,

This is a known limitation of Git integration in Microsoft Fabric / Power BI.

Git integration does not support cross-workspace dependencies. If a report is connected to a semantic model in another workspace, it cannot be fully serialized, which causes commit/download issues in GitHub.

Recommendation:

• Keep the report and semantic model in the same workspace for Git integration
• Cross-workspace semantic models are not supported with Git sync.

Currently, there’s no direct workaround to fully support cross-workspace semantic models with Git integration in Microsoft Fabric.

Possible alternatives:

• Same workspace approach (recommended)
  Keep report + semantic model together for full Git support.
• Duplicate semantic model (workaround)
  Create a copy of the semantic model in the same workspace as the report (can be managed via pipeline/process).
   - Downside: duplication & maintenance overhead.
• Use shared dataset only at runtime
  Develop and manage via Git in same workspace, then switch binding manually after deployment (not fully automated).

Hope this helps!
Kudos are appreciated if you find this useful, and feel free to mark it as the accepted solution.