Use of parameters (dynamic content) for non-fabric sources/destinations

[vivien57]

Hello everyone,

In a Data Pipeline Fabric, I want to make a connection (source or destination) dynamic.

However, in "connection type", as soon as I use "Add dynamic content", I only have Warehouse/Lakehouse/KQL Database.

Is this a limitation which means that connections can only be made dynamic for Fabric elements?

In my example I'd like to make the data source dynamic, which is an On-Premise SQL Server DB (via Gateway)

Thank you in advance for your help

Vivien

[Anonymous · Accepted solution]

Hi @vivien57 ,。

There is a new Data destination feature in Fabric Data Factory's Dataflow Gen2.

That's why the types data destination are shown when you select the connection type. So I think as frithjof_v said, you can post your ideas to Idea or vote for Ideas with similar ideas to yours.

Best Regards

Yilong Zhou

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[frithjof_v]

Please vote here:

Parameterization support for connection

https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=a954f6cf-891f-ee11-a81c-000d3ae64e06

Parameterize Connection Strings

https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=f92a2892-e62f-ef11-a296-6045bdb21058

Data Pipelines - Create Relative Connection to Warehouse/Lakehouse/KQL DB

https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=2b27063b-212a-ef11-8ee7-6045bd80ecff

Connections should be parameterized to allow for connections across multiple similar connection types

https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=cd5ccbf7-391c-ee11-a81c-6045bd7e3068

Deployment Rules for Data Pipelines

https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=41ce7bd9-262a-ef11-8ee7-6045bd80ecff