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.

GQ00's avatar
GQ00
Helper III
2 months ago

Hi,

 

Thanks so much for your help. I can confirm adjusting the data source on the thin reports, syncing to GIT, pulling from Dev and then running deployment pipeline fixed autobinding in Test (test thin report targets test SM).

 

However I now have another issue hopefully you can help me with. When looking at the comparison between test and prod in deployment pipelines, the semantic model is flagged as New in Test and Not in previous starget in Prod, despite having the same name. I'd rather avoid deleting the SM from prod as it contains several years of data; is there a way to fix this binding between Test and Prod now?

 

Thank you!

 

EDIT: Quick google search suggested reassigning the prod workspace to the deployment pipeline, however that did nto fix the issue. Please note the SM in prod is also referenced in pipelines, as such I'm hesitant to delete it. How can I tell DP that SM in Test shoudl be link to the SM in prod ?

 

TIA

 

EDIT2: DP is now linking the SM correctly. Deploying end to end was a success, THANK YOU!

GQ00's avatar
GQ00
Helper III
2 months ago

Yet another update, it seems changing branhces in Dev breaks autobinding again... is that the same experience everyone is having? Are we not meant to change branches despiten the fabric UI allow it?