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!!