Deployment Pipeline Error on Semantic model dataset

[tzee]

I created a deployment pipeline for 1 simple report in power bi service.  This report is using a semantic model from another workspace. We have been using it for over 2 months now.  I recently setup up a PROD enviroment for the report, so that we can make changes to the data without impacting the live report. The first 3 days off deployment went perfectly fine. But then on day 4 i started getting the attached error during deployment.  I'm not sure what to do, as the report works with the linked semantic model, it just wont deploy in the pipeline.  How do i get around this so that we can deploy the changes through the pipeline.

Update: I figured out the issue. Turns out, because i created another deployment Pipeline on the workspace with the semantic model, this for some reason cut off the connection to the report that i had on the other workspace.  For now im good, but i need to create a pipeline for my semnatic model and warehouse soon , so this will impact me again. How do i get around this?

[v-prasare]

Hi @tzee,

We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.

@Vinodh247 ,Thanks for your prompt response

Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support

[teelee]

im still working throught this.

[Vinodh247]

When you create a deployment pipeline for the workspace hosting the semantic model, PBI automatically changes its internal binding context. As a result any report in another workspace linked to that model will lose its conn during deployment.

Pls try this, i think one of them will work for you I believe. 

Keeping your semantic model in a dedicated workspace that is not part of any deployment pipeline, you can use it as a certified or shared dataset. Do not assign the same workspace to multiple deployment pipelines. If you must pipeline both the report and dataset, use parameter or dataset binding rules in the pipeline to rebind the report to the correct dataset in each stage (dev / tst / prod).

[teelee]

If the recommendation is to keep the semantic model from a deployment model, how to do have a test version that can be moved to prod easily? We need to test without touching prod and push quickly for production migration. My warehouse and dataflows will be in the deployment pipeline on the same workspace. 

Here is the layout of my environments:

Reports: DEV  Workspace_1  --> PROD Workspace_1

Datawarehouse/Lakehouse/Dataflows / Semantic Model: DEV Workspace_2 --> PROD Workspace_2 (this deployment was inactivated after i relized the conflict with the Reports.  - but will be reset up with everything but the Semantic Model (until i can figure out how to handle this).

Data Pipelines: Dev Workspace_3 --> PROD Workspace_3

Our IT team has required us to split the Data engineering workspaces from the reporting workspaces.

*Note none of these are using the same staging workspaces.

How do i add deployment pipeline rules. I dont see an option to add rules in the settings, is this a tenant level setting?