Forum Discussion
Fabric data pipeline Variables for deployment
Hi,
I have Fabric Prod WS and Dev WS. When i move code from Dev WS into prod WS. The prod pipelines still points to dev WS. So i variablized the connections, workspace, WH.
Parent pipeline - picks up looksup list of tables to be processed from ETLConfigTable.
Foreach loop invokes child pipeline which has copy activity.
within foreach loop --> invoking child pipeline. I cant be adding child pipeline id since there are 20-30 child pipelines. How will i know child pipeline id when code moves into prod. I cant be changing / assigning pipeline id between dev and prod whenever code is moved. Am i missing something?
Similar to ADF cant fabric pipelines be referrenced with pipeline name?
whats the best way to parameterize and move fabric parent/ child pipeline (ESPECIALLY INVOKING CHILD PIPELINES) between dev prod workspaces, and pointing sources, connections and workspace appropriately.
Thanks for your help.
Hi AJAJ
Thank you for reaching out to the Microsoft Fabric community forum.The behavior you’re experiencing with the Invoke Pipeline activity is expected due to current Fabric limitations, rather than a configuration issue. When the Workspace property is parameterized, the activity cannot enumerate child pipelines at design time, which leaves the dropdown empty and can make parameter bindings seem inconsistent. This is because Fabric identifies pipelines using the Workspace ID and Pipeline ID (GUID), and the UI only supports static, design-time pipeline selection, not dynamic expressions.
The legacy Invoke Pipeline activity only works within the same workspace, while the preview version allows cross-workspace invocation, but only if Workspace ID and Pipeline ID are specified as GUIDs. It cannot resolve pipeline names when the workspace is parameterized.
Deployment pipelines also do not remap pipeline references, they only remap connections and parameters, so a Dev pipeline GUID won’t automatically map to a Prod GUID during promotion.
As a workaround, you can provide the Pipeline ID dynamically at runtime using a configuration table, Variable Library, or REST lookup, or consider using a metadata-driven pipeline until Fabric offers full support for dynamic, cross-workspace pipeline binding.
For more details ,please refer to the Microsoft official documentation on
Invoke pipeline activity - Microsoft Fabric | Microsoft Learn
I hope this helps. If you have more questions, feel free to ask and we’ll be glad to assist further.
Best Regards,
Microsoft Fabric Community Support Team.
1 Reply
Hi AJAJ
Thank you for reaching out to the Microsoft Fabric community forum.The behavior you’re experiencing with the Invoke Pipeline activity is expected due to current Fabric limitations, rather than a configuration issue. When the Workspace property is parameterized, the activity cannot enumerate child pipelines at design time, which leaves the dropdown empty and can make parameter bindings seem inconsistent. This is because Fabric identifies pipelines using the Workspace ID and Pipeline ID (GUID), and the UI only supports static, design-time pipeline selection, not dynamic expressions.
The legacy Invoke Pipeline activity only works within the same workspace, while the preview version allows cross-workspace invocation, but only if Workspace ID and Pipeline ID are specified as GUIDs. It cannot resolve pipeline names when the workspace is parameterized.
Deployment pipelines also do not remap pipeline references, they only remap connections and parameters, so a Dev pipeline GUID won’t automatically map to a Prod GUID during promotion.
As a workaround, you can provide the Pipeline ID dynamically at runtime using a configuration table, Variable Library, or REST lookup, or consider using a metadata-driven pipeline until Fabric offers full support for dynamic, cross-workspace pipeline binding.
For more details ,please refer to the Microsoft official documentation on
Invoke pipeline activity - Microsoft Fabric | Microsoft Learn
I hope this helps. If you have more questions, feel free to ask and we’ll be glad to assist further.
Best Regards,
Microsoft Fabric Community Support Team.