Forum Discussion
Deployment Pipeline Error
Hi km267
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
Thank you.
I did not write this expression @pipeline().DataFactory on purpose. I simply selected the Workspace ID found in system variable and it returned this - @pipeline().DataFactory. If this doesn't belong in fabric it may need to be removed.
Are you asking that I hardcode the workspace id as a parameter? If so, does this not then mean that I have to hardcode it across all 3 environments? This defeats the purpose of the deployment. It still didn't work when I tried it. I still got same error: Import failure: "RequestValidationFailed. 'WorkspaceId' cannot be null".
Hi km267
The error "RequestValidationFailed. 'WorkspaceId' cannot be null" occurs because the @pipeline().DataFactory expression automatically inserted when selecting Workspace ID in Microsoft Fabric is an Azure Data Factory system variable that is not supported in Fabric. Consequently, it resolves to null during deployment, causing the failure.
Moreover, Microsoft Fabric currently does not support deployment pipeline parameter rules for data pipeline connection properties such as workspaceId and artifactId. This limitation likely explains why your parameter-based deployment approach also failed, despite following the correct pattern for defining and referencing parameters.
As a workaround, you can use a Web activity at the beginning of your pipeline to dynamically retrieve the required connection metadata, such as workspaceId and artifactId (e.g., a lakehouse or warehouse ID), via the Microsoft Fabric REST API, specifically the “List items” endpoint under Lakehouses or Warehouses. Store the retrieved values in pipeline variables using a Set Variable activity.
To call the API, configure the Web activity with OAuth 2.0 authentication using an Azure AD app registration that has the necessary Microsoft Graph or Fabric-specific permissions. Parse the JSON response using an expression or data flow, extract the required ID(s), and assign them to variables.
For more detailed understanding, please refer
Dynamic Warehouse & Lakehouse Connections in Microsoft Fabric Data Pipelines | Under the kover of business intelligence
If this post helps, kindly mark it as Accepted Solution.
Thank You!