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.

Kedar_Pande's avatar
Kedar_Pande
Super User
2 months ago

  

Copilot's right. PBIP + TMDL + Git fixes all of it.

 

 

  • Save the model as PBIP, it becomes TMDL text you can bulk-edit and diff.
  • Keep thin reports as separate PBIP files in the same repo.
  • Deploy via Fabric Git or fabric-cicd, drop the manual ALM pushes.

     

     

GQ00

  • GQ00's avatar
    GQ00
    Helper III
    2 months ago

    hi Kedar_Pande ,

     

    thanks for your answer.

     

    I recently came to the conclusion that our reporting assets (semantic model and lean reports) should exists in a PPU workspace, this is because of the high CU consumption during report usage (I'm talking about two users throttling an F16 workspace exclusively dedicated to reporting within minutes).

     

    Am I correct in saying that Fabric Git requires a fabric workspace? and if so, can you suggest how to work around this limitation, incorporating CI/CD while maintaning the reporting assets in PPU?

     

    thanks,

     

    *EDIT* Perhaps Git to Dev WS (fabric), and deployment pipeline to Prod WS (PPU) ?
    Should there be a more striaghtfoward way? Am I missing something?