Forum Discussion
Advocate IIAny alternative solutions for Deploying Data Pipeline Connections?
I found a workaround that allows me to proceed, not quite as elegant as having connections at the workspace level but has the desired end result.
On the destination connection, selecting 'Dynamic Input' on the connection type - this exposes the workspace id and sql connection string that can then be parameterised. These values can then be stored as config in a control database (schema within Data Warehouse or file in the Lakehouse) and setup in a previous step in the pipeline. The end result is the same as in the Azure Resource Group based solution mentioned above.
Advocate III found a workaround that allows me to proceed, not quite as elegant as having connections at the workspace level but has the desired end result.
On the destination connection, selecting 'Dynamic Input' on the connection type - this exposes the workspace id and sql connection string that can then be parameterised. These values can then be stored as config in a control database (schema within Data Warehouse or file in the Lakehouse) and setup in a previous step in the pipeline. The end result is the same as in the Azure Resource Group based solution mentioned above.
Hi DanielAmbler ,
Glad to know that you were able to get to a resolution. Please continue using Fabric Community on your further queries.