Forum Discussion
Dataflow Gen2 accepting Parameters-Values from Notebook - HELP
Thank you for reaching out to the Microsoft Fabric Community Forum.
In Dataflow Gen2, public parameters must be explicitly defined within the dataflow before they can be overridden via a pipeline or REST API. If you're unable to see the parameter in the pipeline’s Dataflow activity settings, it likely means either the parameter hasn't been marked as public or its usage is not supported for override.
To make parameters available for pipeline integration, open your Dataflow Gen2 in Power Query, create the required parameters under "Manage Parameters" (e.g., SQLHostName), use them in your queries such as in the SQL Server connection string, and mark them as public so they can be overridden externally.
To pass parameters via a pipeline, add a Dataflow activity, select the appropriate Dataflow Gen2, and under the Parameters section, bind the listed public parameters to pipeline variables or notebook outputs.
Currently, Dataflow Gen2 does not support overriding the resource path of a data source (e.g., dynamically changing the SQL Server hostname). Even if you pass a different value, the connection string remains fixed to what was authored in the dataflow. This is a known limitation in the public preview of parameter support.
As a work around this limitation, create a generic dataflow template with a placeholder hostname, then use notebooks or pipelines to dynamically copy and deploy the dataflow with the correct hostname injected into the query or connection string, or alternatively, perform the data extraction directly in notebooks and write the results to a Lakehouse.
For more details, refer to the official documentation on Dataflow Gen2 parameters.
If this response resolves your query, kindly mark it as the Accepted Solution to help other community members. A Kudos is also appreciated if you found the response helpful.
Thank you!
Community Support
Thank you for reaching out to the Microsoft Fabric Community Forum.
In Dataflow Gen2, public parameters must be explicitly defined within the dataflow before they can be overridden via a pipeline or REST API. If you're unable to see the parameter in the pipeline’s Dataflow activity settings, it likely means either the parameter hasn't been marked as public or its usage is not supported for override.
To make parameters available for pipeline integration, open your Dataflow Gen2 in Power Query, create the required parameters under "Manage Parameters" (e.g., SQLHostName), use them in your queries such as in the SQL Server connection string, and mark them as public so they can be overridden externally.
To pass parameters via a pipeline, add a Dataflow activity, select the appropriate Dataflow Gen2, and under the Parameters section, bind the listed public parameters to pipeline variables or notebook outputs.
Currently, Dataflow Gen2 does not support overriding the resource path of a data source (e.g., dynamically changing the SQL Server hostname). Even if you pass a different value, the connection string remains fixed to what was authored in the dataflow. This is a known limitation in the public preview of parameter support.
As a work around this limitation, create a generic dataflow template with a placeholder hostname, then use notebooks or pipelines to dynamically copy and deploy the dataflow with the correct hostname injected into the query or connection string, or alternatively, perform the data extraction directly in notebooks and write the results to a Lakehouse.
For more details, refer to the official documentation on Dataflow Gen2 parameters.
If this response resolves your query, kindly mark it as the Accepted Solution to help other community members. A Kudos is also appreciated if you found the response helpful.
Thank you!