Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Data Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more

Reply
svac
New Member

Dataflow Activity Parameters Lose Expression and Get Hardcoded After Reopening Pipeline

Hi! I’m using a Dataflow Gen2 activity in a Fabric pipeline and passing parameters via dynamic content (pipeline library variables).

When I configure the parameters, they are correctly stored as expressions:
 
"value": {
"value":
"@pipeline().libraryVariables.Data_engineering_Variable_Library_workspace_id",
"type": "Expression"
}
 
The pipeline validates and saves successfully. However, when I reopen the pipeline, Fabric rewrites the parameter values as evaluated static string:
 
"value": "f31c2823-10f1-4e97-bc15-6f39f4981d57",
"type": "String"
 
This removes the expression and effectively hardcodes the value.
  • Is there a supported way to persist dynamic expressions for Dataflow Gen2 parameters in pipeline activities?
  • Are there recommended patterns for passing workspaceId/lakehouseId dynamically without the UI flattening expressions?

Thanks!!

0 REPLIES 0

Helpful resources

Announcements
Fabric Data Days is here Carousel

Data Days 2026

Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.

June Fabric Update Carousel

Fabric Monthly Update - June 2026

Check out the June 2026 Fabric update to learn about new features.

Top Solution Authors