Forum Discussion
Deployment Pipeline Error on Semantic model dataset
Super UserWhen 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).
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?
