Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Special holiday offer! You and a friend can attend FabCon with a BOGO code. Supplies are limited. Register now.
Hi everyone I'm having an issue passing parameters into the invoke Dataflow activity for a pipeline.
When I pass in workspace and dataflow Id parameters I see in the input the following
{
"dataflowId": XXX
"workspaceId":YYY
"notifyOption" : "NoNotification"
}
and then the Dataflow can't be run
However when I manually write in the workspace and Dataflow that I want to use I get the same but with an additional item in the list
{
"dataflowId": XXX
"workspaceId":YYY
"notifyOption" : "NoNotification"
"dataflowType":DataflowFabric"
}
I'm assuming that dataFlowType means that the Dataflow is successfully invoked but there is no field to enter it in the settings tab. Am I missing something in how I'm using the parameters in my pipeline to invoke the Dataflow?
Solved! Go to Solution.
Hi @BriefStop ,
Thank you for reaching out to Microsoft Community.
When workspaceId and dataflowId are passed in as parameters, the Invoke Dataflow activity only receives those values. In this scenario, the activity doesn’t automatically detect the type of dataflow, so the dataflowType property is not added. Without this field, the request is incomplete, which is why the dataflow doesn’t run. When you manually select the workspace and dataflow in the UI, Fabric is able to identify the type and automatically includes:
"dataflowType": "DataflowFabric"
This property tells the activity whether it’s working with a Fabric Dataflow Gen2 or a Power BI Dataflow Gen1. Since the UI handles this automatically—but parameterization does not—you need to add it manually. To fix the issue, open the Invoke Dataflow activity, switch to the JSON/Advanced view, and add the dataflowType field alongside your parameter references:
"dataflowId": "@pipeline().parameters.dataflowId",
"workspaceId": "@pipeline().parameters.workspaceId",
"dataflowType": "DataflowFabric",
"notifyOption": "NoNotification"
Once this is included, the activity will run correctly with parameters.
Hope this helps.
Thank you.
Hi @BriefStop ,
May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.
Thank you.
Hi @BriefStop ,
I just wanted to check if the issue has been resolved on your end, or if you require any further assistance. Please feel free to let us know, we’re happy to help!
Thank you
Chaithra E.
Hi @BriefStop ,
Thank you for reaching out to Microsoft Community.
When workspaceId and dataflowId are passed in as parameters, the Invoke Dataflow activity only receives those values. In this scenario, the activity doesn’t automatically detect the type of dataflow, so the dataflowType property is not added. Without this field, the request is incomplete, which is why the dataflow doesn’t run. When you manually select the workspace and dataflow in the UI, Fabric is able to identify the type and automatically includes:
"dataflowType": "DataflowFabric"
This property tells the activity whether it’s working with a Fabric Dataflow Gen2 or a Power BI Dataflow Gen1. Since the UI handles this automatically—but parameterization does not—you need to add it manually. To fix the issue, open the Invoke Dataflow activity, switch to the JSON/Advanced view, and add the dataflowType field alongside your parameter references:
"dataflowId": "@pipeline().parameters.dataflowId",
"workspaceId": "@pipeline().parameters.workspaceId",
"dataflowType": "DataflowFabric",
"notifyOption": "NoNotification"
Once this is included, the activity will run correctly with parameters.
Hope this helps.
Thank you.