Forum Discussion

GQ00's avatar
GQ00
Helper III
2 months ago
Solved

Efficient development with lean reports and huge Semantic Model

We currently have a semantic model (import mode) with incremental refresh in the cloud and build lean reports on top of it. The end result is that when editing the SM one needs to open PBIX-base e...
Need Help
  • v-abhinavmu's avatar
    v-abhinavmu
    2 months ago

    Hi GQ00,

    Thanks for the update, and I'm glad to hear the deployment is now working.

     

    Deployment pipelines maintain connections between dependent items through Autobinding. For Autobinding to succeed:

    • The semantic model that the report depends on must exist in the corresponding target stage.
    • If the dependent semantic model isn't present in the target stage, the deployment fails. In such cases, you can use Select related to deploy all dependent items together.
    • You can also use View lineage to verify that the report is connected to the expected semantic model before deployment.

    For more information, please refer to the following documentation:
    The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft Learn

     

    If you continue to experience the issue after verifying these points, please let us know and we'll be happy to assist further.

     

    Thank you.

v-abhinavmu's avatar
v-abhinavmu
Community Support
2 months ago

Hi GQ00,

Thanks for reaching out to the Microsoft Fabric Community forum.

 
Your understanding is correct. Fabric Git integration is currently supported only for workspaces backed by Fabric capacity, so a standalone PPU workspace cannot be connected directly to a Git repository.


In this scenario, a common approach is to use a Fabric-backed Development workspace for PBIP/TMDL development and Git integration, then promote the validated changes to your PPU Production workspace through a deployment pipeline or an automated CI/CD process. This lets you maintain source control and collaborative development while keeping your production reporting assets in PPU if that best suits your workload.


Therefore, your proposed workflow Git → Fabric Dev Workspace → Deployment Pipeline/CI-CD → PPU Production Workspace is the recommended approach.

 

You can also refer to the Microsoft documentation on Fabric Git integration prerequisites for more details: 
https://learn.microsoft.com/fabric/cicd/git-integration/git-get-started 

 

I hope this helps. Please feel free to reach out if you have any further questions.
Thank you.

 

 

  • GQ00's avatar
    GQ00
    Helper III
    2 months ago

    hi , thanks for your answer 

     

    I ended up with 3 WS , Dev (fabric with git) test and prod 

     

    the issue now is that deployment pipelines deploys reports that are linked to the prod semantic model. I thought they would natively know they are suppose to connect to the model in their deployment stage.

     

    I've looked into this further and it seems auto binding failed and that I need to figure something out with semantic links ? please tell me there is an easier way feels that connecting to the SM in their workspace should be the default behaviour.

     

    thanks for your help