Forum Discussion

Matthew_G's avatar
Matthew_G
Icon for Advocate I rankAdvocate I
2 years ago
Solved

Dynamic pipelines to use across workspaces

Hi fellow Fabricators,   The set-up: Currently you can't use a deployment pipleline to deploy data pipelines. We have three different workspaces, basically dev, test, prod - we did it this way to ...
pipelines
  • Anonymous's avatar
    Anonymous
    2 years ago

    Hi Matthew_G 
    Thanks for using Fabric Community.
    You need to select the "Add dynamic content" option within the drop down and pass in the GUID.

     


    You need to create a new parameter for the stored procedure activity.
    The parameter value should be Lakehouse/Data Warehouse/KQL Database object ID. To get your Lakehouse/Data Warehouse/KQL Database object ID, open your Lakehouse/Data Warehouse/KQL Database in your workspace, and the ID is after /lakehouses/or /datawarehouses/ or /databases/ in your URL.

     

     


    Please refer to this link for more information: Link1
    Hope this helps. Please let me know if you have any further questions.

  • Matthew_G's avatar
    Matthew_G
    2 years ago

    Thanks, it looks a bit different for the Stored Procedure Activity.

    When you add dynamic content to the Warehouse it then also requests a SQL connection string.

    I then added two parameters, the connection string and the warehouse guid, adding it as dynamic content.

    This now works.

     

     

     

     

HappyFabric's avatar
HappyFabric
Icon for Microsoft Employee rankMicrosoft Employee
2 years ago

 

I would like to do something similar with referencing my local lakehouse. I want to have lakehouses of the same name in each of my testing, staging, and prod workspaces.  How can I reference the lakehouse of the name "My_Lakhouse" in this local workspace?  Something like  My_Lakehouse.@pipeline().DataFactory   ?