Forum Discussion
Helper IVParameterized connections in Data pipelines
Hello v-saisrao-msft ,
sorry, but your answer doesn't help me.
I don't know if it is working or not, and it is no documentation how it works...
For all others who want to use the feature: For my case i works, when i use the connection id as parameter in "connection". To get the connectionid, I stored the fixed connection and found the id in the json.
Community SupportHi cw88,
You're absolutely right to highlight this behavior, and thanks for testing the new feature. I'd like to follow up on my previous response with some clarification. While parameterizing the connection name using a pipeline parameter (e.g., @pipeline().parameters.ConnectionName) is indeed a capability introduced in the March update of Microsoft Fabric, it appears that this functionality is not yet fully supported for on-premises SQL Server connections configured via the On-premises Data Gateway.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
Helper IVHello v-saisrao-msft ,
sorry, but your answer doesn't help me.
I don't know if it is working or not, and it is no documentation how it works...
For all others who want to use the feature: For my case i works, when i use the connection id as parameter in "connection". To get the connectionid, I stored the fixed connection and found the id in the json.
- v-saisrao-msft
Hi cw88,
Thanks for the follow-up, and I really appreciate you taking the time to share your working approach this will definitely help others running into the same issue.Using the connection ID (instead of the connection name) as a parameter and retrieving it from the exported pipeline JSON is a smart and effective workaround for on-prem SQL Server connections via the Gateway.
Please Mark your approach as the accepted solution so other community members can find it more quickly. Thanks again for helping drive clarity on this new feature!
